Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dc59131859c0e190a4d6c3621dd295e73304c089c744adcf7a2f7b73f00911a

Tx prefix hash: 646250d7fadb9f64dcb6421c43c60b9db824ca2932cc53fd26508f838d8d5d11
Tx public key: d554f2c2ca8bc817acb36a8dfc6d2359c6307e1244530f0a158b0e16b56f3cec
Timestamp: 1750852085 Timestamp [UCT]: 2025-06-25 11:48:05 Age [y:d:h:m:s]: 00:147:12:22:11
Block: 1312495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103377 RingCT/type: yes/0
Extra: 01d554f2c2ca8bc817acb36a8dfc6d2359c6307e1244530f0a158b0e16b56f3cec02110000000943846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da21e8d38b00fb354134766e8fc0864aae655f472a8d240a4a33942c628e565d 0.600000000000 1800128 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": 1312505, "vin": [ { "gen": { "height": 1312495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da21e8d38b00fb354134766e8fc0864aae655f472a8d240a4a33942c628e565d" } } ], "extra": [ 1, 213, 84, 242, 194, 202, 139, 200, 23, 172, 179, 106, 141, 252, 109, 35, 89, 198, 48, 126, 18, 68, 83, 15, 10, 21, 139, 14, 22, 181, 111, 60, 236, 2, 17, 0, 0, 0, 9, 67, 132, 109, 102, 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