Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39c7d59e63ea9ffbab3fb0ab87b1cf98cf1a56d14f2e36b517896d6a2de70de8

Tx prefix hash: 068d95ac9da4475a40616806393c2d787306e8e478016ca583656958ed00ba2d
Tx public key: aea7532bb2b098459bfe22dca51a50e2674704d0b7ecff12fcc6cf3f1ec21b6e
Timestamp: 1727411282 Timestamp [UCT]: 2024-09-27 04:28:02 Age [y:d:h:m:s]: 01:044:09:36:28
Block: 1118999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290127 RingCT/type: yes/0
Extra: 01aea7532bb2b098459bfe22dca51a50e2674704d0b7ecff12fcc6cf3f1ec21b6e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59571bd7f84afa52cbcc7cba1fd4f0d4d45e63b5777d91bd0442a3adb0dbc752 0.600000000000 1600392 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": 1119009, "vin": [ { "gen": { "height": 1118999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59571bd7f84afa52cbcc7cba1fd4f0d4d45e63b5777d91bd0442a3adb0dbc752" } } ], "extra": [ 1, 174, 167, 83, 43, 178, 176, 152, 69, 155, 254, 34, 220, 165, 26, 80, 226, 103, 71, 4, 208, 183, 236, 255, 18, 252, 198, 207, 63, 30, 194, 27, 110, 2, 17, 0, 0, 0, 4, 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