Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2ce782edb41bd503c46d5ae8438af2d2c9b7eb2f8dd51808c725c900ce1dbf84

Tx prefix hash: 2441acac8b80de21ab12f575e5536aac7299dbd1dbe88baa317c4747ef06f456
Tx public key: 020fc45e039446cb01f3974bd1b7314336c16b98c1d7d0f3d60117878d1d425d
Timestamp: 1732495994 Timestamp [UCT]: 2024-11-25 00:53:14 Age [y:d:h:m:s]: 00:121:05:45:38
Block: 1161055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86446 RingCT/type: yes/0
Extra: 01020fc45e039446cb01f3974bd1b7314336c16b98c1d7d0f3d60117878d1d425d0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8342a78adb7c7ebee83130f2bfb97aa83c55a35e4cea820223e5c4730fc87ef9 0.600000000000 1646706 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1161065, "vin": [ { "gen": { "height": 1161055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8342a78adb7c7ebee83130f2bfb97aa83c55a35e4cea820223e5c4730fc87ef9" } } ], "extra": [ 1, 2, 15, 196, 94, 3, 148, 70, 203, 1, 243, 151, 75, 209, 183, 49, 67, 54, 193, 107, 152, 193, 215, 208, 243, 214, 1, 23, 135, 141, 29, 66, 93, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8