Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4d224b00a6f9f04564f936049d8b72ce92b6dd81b02bf80a079248ecd34c924

Tx prefix hash: 920d29c0584c9ac125d7a1afe16285d84a245bcfae12b2b503050bc82e618525
Tx public key: 17a3402ed9a9e480c3d34eba38202bc7a263baca3a41c9de0af6b82f61ce8bcf
Timestamp: 1701450240 Timestamp [UCT]: 2023-12-01 17:04:00 Age [y:d:h:m:s]: 01:122:04:16:17
Block: 903764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348464 RingCT/type: yes/0
Extra: 0117a3402ed9a9e480c3d34eba38202bc7a263baca3a41c9de0af6b82f61ce8bcf02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.621519381000 dcy

stealth address amount amount idx
00: ba013a8da03f783ff285d599a6ff28b1718c64625071386cc7c03eeeff17bc98 0.621519381000 1360455 of 0

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": 903774, "vin": [ { "gen": { "height": 903764 } } ], "vout": [ { "amount": 621519381, "target": { "key": "ba013a8da03f783ff285d599a6ff28b1718c64625071386cc7c03eeeff17bc98" } } ], "extra": [ 1, 23, 163, 64, 46, 217, 169, 228, 128, 195, 211, 78, 186, 56, 32, 43, 199, 162, 99, 186, 202, 58, 65, 201, 222, 10, 246, 184, 47, 97, 206, 139, 207, 2, 17, 0, 0, 0, 5, 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