Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beaf9d69879ee25fcfc3c2b7355a6c32dd645abcd8f5c70679f60658021aa9f8

Tx prefix hash: 420c3beed4b29eba9bee6c0506d9cefe98c4a450d3fa41f86bd21e33832e2d6a
Tx public key: afc4e97a7d5ba2fed75e8dcc4156b199de897fdf74ae64c1ba2bf2e4cd502672
Timestamp: 1735934106 Timestamp [UCT]: 2025-01-03 19:55:06 Age [y:d:h:m:s]: 00:102:17:24:25
Block: 1189531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73204 RingCT/type: yes/0
Extra: 01afc4e97a7d5ba2fed75e8dcc4156b199de897fdf74ae64c1ba2bf2e4cd50267202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffdd418add91b2951c52149411a60af74d1109bc424926a48c3b61e1a143539f 0.600000000000 1676042 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": 1189541, "vin": [ { "gen": { "height": 1189531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffdd418add91b2951c52149411a60af74d1109bc424926a48c3b61e1a143539f" } } ], "extra": [ 1, 175, 196, 233, 122, 125, 91, 162, 254, 215, 94, 141, 204, 65, 86, 177, 153, 222, 137, 127, 223, 116, 174, 100, 193, 186, 43, 242, 228, 205, 80, 38, 114, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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