Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a187008af2f7ac49b4e540405699712347dc890c55cb11ed751367b637f272d

Tx prefix hash: 5bd82106d073867cb56757daaa39bf3171da522efb27c6fae3a818ed46505d1e
Tx public key: 8426142bfdd09c9d5a320257e4dcb8223d585e720327aa9d33b8049cab0e5acb
Timestamp: 1761487148 Timestamp [UCT]: 2025-10-26 13:59:08 Age [y:d:h:m:s]: 00:014:05:40:12
Block: 1398387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10196 RingCT/type: yes/0
Extra: 018426142bfdd09c9d5a320257e4dcb8223d585e720327aa9d33b8049cab0e5acb021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c2de05aea72a324b241159cc414a0314dcc8e01a76ada4c6cd38f165f32e937 0.600000000000 1886684 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": 1398397, "vin": [ { "gen": { "height": 1398387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c2de05aea72a324b241159cc414a0314dcc8e01a76ada4c6cd38f165f32e937" } } ], "extra": [ 1, 132, 38, 20, 43, 253, 208, 156, 157, 90, 50, 2, 87, 228, 220, 184, 34, 61, 88, 94, 114, 3, 39, 170, 157, 51, 184, 4, 156, 171, 14, 90, 203, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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