Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b2122551ee1dacd037eea99722f9941b96d2fd64f69c8140e9f62a606de613e

Tx prefix hash: 5a39527e76f7f345e2a32823c1fb5e8a1190c2b3bbe7949617596c59d4b1085f
Tx public key: de2579d3719d5ebbd36d486391fd827db077d7bff83da9ae9cc92164d1caf9a4
Timestamp: 1736398750 Timestamp [UCT]: 2025-01-09 04:59:10 Age [y:d:h:m:s]: 00:076:02:33:15
Block: 1193366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54165 RingCT/type: yes/0
Extra: 01de2579d3719d5ebbd36d486391fd827db077d7bff83da9ae9cc92164d1caf9a4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 980a41e1bd572310973d9b5a6ce0293db5a2a0de2abab923b64094e39a8bf444 0.600000000000 1679925 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": 1193376, "vin": [ { "gen": { "height": 1193366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "980a41e1bd572310973d9b5a6ce0293db5a2a0de2abab923b64094e39a8bf444" } } ], "extra": [ 1, 222, 37, 121, 211, 113, 157, 94, 187, 211, 109, 72, 99, 145, 253, 130, 125, 176, 119, 215, 191, 248, 61, 169, 174, 156, 201, 33, 100, 209, 202, 249, 164, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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