Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74d8f8960e0cb74a89e3f74044e2213d14bf3afffc7725e2fe78714e4de31640

Tx prefix hash: fe59f777a9abb2a70615cc1d5cf2195dcf500270bc64891f7a340dfe2a6498ca
Tx public key: 5f21d4d20f2aa79e5202e1ba4c89c820f38e74df572c3d216212c114a708f97a
Timestamp: 1749864630 Timestamp [UCT]: 2025-06-14 01:30:30 Age [y:d:h:m:s]: 00:155:00:57:40
Block: 1304506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108573 RingCT/type: yes/0
Extra: 015f21d4d20f2aa79e5202e1ba4c89c820f38e74df572c3d216212c114a708f97a021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0a383d080bb625a876a8eac5ab717552349283fccf39a9edc048e39117aef46 0.600000000000 1792097 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": 1304516, "vin": [ { "gen": { "height": 1304506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a383d080bb625a876a8eac5ab717552349283fccf39a9edc048e39117aef46" } } ], "extra": [ 1, 95, 33, 212, 210, 15, 42, 167, 158, 82, 2, 225, 186, 76, 137, 200, 32, 243, 142, 116, 223, 87, 44, 61, 33, 98, 18, 193, 20, 167, 8, 249, 122, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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