Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8594ab03df695e22128d2d1bd5cdb453a6c386eaa2fb958dbb027aa132fd30c

Tx prefix hash: cc6e33e27021088d6cd58ce50ba2b49a44bfba56467350e882be681a9cc60277
Tx public key: 73fe55822707b1f9665d286c421f9a712c5a8af1b78a837b65d74207fbbb33ba
Timestamp: 1726825877 Timestamp [UCT]: 2024-09-20 09:51:17 Age [y:d:h:m:s]: 00:207:09:04:25
Block: 1114140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148043 RingCT/type: yes/0
Extra: 0173fe55822707b1f9665d286c421f9a712c5a8af1b78a837b65d74207fbbb33ba021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16ad6011dcf92709970c6e1ebd709d00c867644cee66f1e0cd0654d5abeb2cc8 0.600000000000 1593939 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": 1114150, "vin": [ { "gen": { "height": 1114140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16ad6011dcf92709970c6e1ebd709d00c867644cee66f1e0cd0654d5abeb2cc8" } } ], "extra": [ 1, 115, 254, 85, 130, 39, 7, 177, 249, 102, 93, 40, 108, 66, 31, 154, 113, 44, 90, 138, 241, 183, 138, 131, 123, 101, 215, 66, 7, 251, 187, 51, 186, 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