Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51c9486df397f0bea1de0425497e635caaf65ff2070a945ee313d27794fbf7dc

Tx prefix hash: 4e7caeaba8fc8859e8a272f83cefeecb5bf5b5bcc8fa281dc916093600f4f1c2
Tx public key: 88b6fe92ee2e91299a712b26917b030406297a1c580fe1584443f72dace72a5a
Timestamp: 1735354899 Timestamp [UCT]: 2024-12-28 03:01:39 Age [y:d:h:m:s]: 00:105:05:10:18
Block: 1184725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74994 RingCT/type: yes/0
Extra: 0188b6fe92ee2e91299a712b26917b030406297a1c580fe1584443f72dace72a5a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc68bfa03015d641f8ae568d728a1b9ceca9d2e5793c07106f1d4d4173a0ee6b 0.600000000000 1671184 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": 1184735, "vin": [ { "gen": { "height": 1184725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc68bfa03015d641f8ae568d728a1b9ceca9d2e5793c07106f1d4d4173a0ee6b" } } ], "extra": [ 1, 136, 182, 254, 146, 238, 46, 145, 41, 154, 113, 43, 38, 145, 123, 3, 4, 6, 41, 122, 28, 88, 15, 225, 88, 68, 67, 247, 45, 172, 231, 42, 90, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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