Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18ec904dbd453404bf1c22f031835cf3c785f4951cfab48ff9262c1d8d3062e6

Tx prefix hash: 657b286d499bad4b89286607a5dcaa0b8020b2a06a4b011c4302078f55e5157d
Tx public key: d40b481d22cb40285772e0fba37e1b59db966c4efef261d0d1fbf21cc9f9e797
Timestamp: 1731045800 Timestamp [UCT]: 2024-11-08 06:03:20 Age [y:d:h:m:s]: 00:144:15:19:48
Block: 1149046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103182 RingCT/type: yes/0
Extra: 01d40b481d22cb40285772e0fba37e1b59db966c4efef261d0d1fbf21cc9f9e7970211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78dd919c5da409bf75589a13444394edb6e61e6b8d1de139a7d253f3b466eed7 0.600000000000 1634031 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": 1149056, "vin": [ { "gen": { "height": 1149046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78dd919c5da409bf75589a13444394edb6e61e6b8d1de139a7d253f3b466eed7" } } ], "extra": [ 1, 212, 11, 72, 29, 34, 203, 64, 40, 87, 114, 224, 251, 163, 126, 27, 89, 219, 150, 108, 78, 254, 242, 97, 208, 209, 251, 242, 28, 201, 249, 231, 151, 2, 17, 0, 0, 0, 3, 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