Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89e32323a501e5c1a182e03c611ca0b2788fe144933febdbe1c325eff943b856

Tx prefix hash: 0fd66ae63c7dee4b4cc303d82a53acf1a58686179b90b2a4be881e2a462e6c13
Tx public key: 0fedd65e40b051ea8344255b3ed76dd16638d89bf475280d84cd29c75227775d
Timestamp: 1736944374 Timestamp [UCT]: 2025-01-15 12:32:54 Age [y:d:h:m:s]: 00:156:23:09:32
Block: 1197882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111847 RingCT/type: yes/0
Extra: 010fedd65e40b051ea8344255b3ed76dd16638d89bf475280d84cd29c75227775d0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaa8d6b9d411d6a7106c3733e30d961c1d14dcd49a1a3714a5ffdf00191f0306 0.600000000000 1684499 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": 1197892, "vin": [ { "gen": { "height": 1197882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaa8d6b9d411d6a7106c3733e30d961c1d14dcd49a1a3714a5ffdf00191f0306" } } ], "extra": [ 1, 15, 237, 214, 94, 64, 176, 81, 234, 131, 68, 37, 91, 62, 215, 109, 209, 102, 56, 216, 155, 244, 117, 40, 13, 132, 205, 41, 199, 82, 39, 119, 93, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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