Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2def2a6f4d38dcbcb124ea3724a377dfac975b9acb8290a9f3d1149110ea9ed

Tx prefix hash: 1a773c4b37973c4d2e6be840c5256554450679e530b5de1d9c51c4114cf61221
Tx public key: e94e3096bd1fb002e7df928f874c9d63c0048c927682a233bc7f3e7f79f6a0f7
Timestamp: 1721337708 Timestamp [UCT]: 2024-07-18 21:21:48 Age [y:d:h:m:s]: 00:188:01:44:00
Block: 1068659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134506 RingCT/type: yes/0
Extra: 01e94e3096bd1fb002e7df928f874c9d63c0048c927682a233bc7f3e7f79f6a0f702110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d3d23d4dfdd68ec87c4823580235b27750342b70a713e583852eaed20f92016 0.600000000000 1539776 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": 1068669, "vin": [ { "gen": { "height": 1068659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d3d23d4dfdd68ec87c4823580235b27750342b70a713e583852eaed20f92016" } } ], "extra": [ 1, 233, 78, 48, 150, 189, 31, 176, 2, 231, 223, 146, 143, 135, 76, 157, 99, 192, 4, 140, 146, 118, 130, 162, 51, 188, 127, 62, 127, 121, 246, 160, 247, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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