Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaef18216a1d9cb64e4d0a65ee59accd36b32e22704735792175d96b76d7967c

Tx prefix hash: a71bd7f53f98db251d196f8cccefd7144b948081a60f40e0ab3358a053fa7357
Tx public key: e5cd2f27c446bdbf5b807a85ad5e7bd2c08b64d2a55dc1c873dbe82bd5b629d2
Timestamp: 1673073158 Timestamp [UCT]: 2023-01-07 06:32:38 Age [y:d:h:m:s]: 01:330:02:29:13
Block: 669361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496966 RingCT/type: yes/0
Extra: 01e5cd2f27c446bdbf5b807a85ad5e7bd2c08b64d2a55dc1c873dbe82bd5b629d2021100000005faf35c9c000000000000000000

1 output(s) for total of 3.716456896000 dcy

stealth address amount amount idx
00: ed9e390bb7872e3826a3bccf62ea23d60e1029f9f6e6f02d22316ec7f31e6638 3.716456896000 1110672 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": 669371, "vin": [ { "gen": { "height": 669361 } } ], "vout": [ { "amount": 3716456896, "target": { "key": "ed9e390bb7872e3826a3bccf62ea23d60e1029f9f6e6f02d22316ec7f31e6638" } } ], "extra": [ 1, 229, 205, 47, 39, 196, 70, 189, 191, 91, 128, 122, 133, 173, 94, 123, 210, 192, 139, 100, 210, 165, 93, 193, 200, 115, 219, 232, 43, 213, 182, 41, 210, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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