Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a440cb5bef3dfda41d526935e931e6e312a7bdab20fcc6425d9f7bae0338625c

Tx prefix hash: 9519ba60629dd065ee5b43da75fc3e8492c3512f6de8e43a3cbf86ac094bc3b0
Tx public key: 1432adf4e771de138ec6861fc2b614dc0f2b84b17ad2c06eb94f22a522d0ce84
Timestamp: 1720599021 Timestamp [UCT]: 2024-07-10 08:10:21 Age [y:d:h:m:s]: 00:308:16:38:17
Block: 1062533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220576 RingCT/type: yes/0
Extra: 011432adf4e771de138ec6861fc2b614dc0f2b84b17ad2c06eb94f22a522d0ce84021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7983de0535622501ba036be42667a4ddba5874dd569a0797a221fa05c6e1a085 0.600000000000 1533038 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": 1062543, "vin": [ { "gen": { "height": 1062533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7983de0535622501ba036be42667a4ddba5874dd569a0797a221fa05c6e1a085" } } ], "extra": [ 1, 20, 50, 173, 244, 231, 113, 222, 19, 142, 198, 134, 31, 194, 182, 20, 220, 15, 43, 132, 177, 122, 210, 192, 110, 185, 79, 34, 165, 34, 208, 206, 132, 2, 17, 0, 0, 0, 1, 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