Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee5e2dcff6cfe3632e00a21cc026af4cf82aa5cb7097d04e93e6a7307538599

Tx prefix hash: 93419e53b821ce29d4678b4a9cddaceb5197941834d6c1d1c4d632c80ec81a74
Tx public key: 8dee6ac08d0f7efc559612010abed9868597edab719c500e002705e7c4f5d6f4
Timestamp: 1702899995 Timestamp [UCT]: 2023-12-18 11:46:35 Age [y:d:h:m:s]: 01:180:15:03:51
Block: 915785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390182 RingCT/type: yes/0
Extra: 018dee6ac08d0f7efc559612010abed9868597edab719c500e002705e7c4f5d6f402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f9658103dd542f9a9dcc2903c921d0ce19f189e028a5e3ceb448d92092bd1dd 0.600000000000 1373209 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": 915795, "vin": [ { "gen": { "height": 915785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f9658103dd542f9a9dcc2903c921d0ce19f189e028a5e3ceb448d92092bd1dd" } } ], "extra": [ 1, 141, 238, 106, 192, 141, 15, 126, 252, 85, 150, 18, 1, 10, 190, 217, 134, 133, 151, 237, 171, 113, 156, 80, 14, 0, 39, 5, 231, 196, 245, 214, 244, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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