Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0a5f125f888e37a4b2c93d8b4b3586f4036f9f0c944c29e157681ac95ff0ef

Tx prefix hash: ccdf8b0592cfa64db2641de4adcd4ced7ffef3f82e134da5aee73276335a3d31
Tx public key: 38e9712fe8aeab62a6b8278bfe65756994c21d9a39cd491d1b1bf2dcaa02a670
Timestamp: 1708900644 Timestamp [UCT]: 2024-02-25 22:37:24 Age [y:d:h:m:s]: 01:078:23:00:13
Block: 965543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317473 RingCT/type: yes/0
Extra: 0138e9712fe8aeab62a6b8278bfe65756994c21d9a39cd491d1b1bf2dcaa02a6700211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dae3b0ea0ed7cf25af781a1eebfeb4c77fad376966152ba74093771f3ca61294 0.600000000000 1425296 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": 965553, "vin": [ { "gen": { "height": 965543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dae3b0ea0ed7cf25af781a1eebfeb4c77fad376966152ba74093771f3ca61294" } } ], "extra": [ 1, 56, 233, 113, 47, 232, 174, 171, 98, 166, 184, 39, 139, 254, 101, 117, 105, 148, 194, 29, 154, 57, 205, 73, 29, 27, 27, 242, 220, 170, 2, 166, 112, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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