Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b92c48f17f21bf05748c5634c1828905f8da1ae7c50c28e856ea764c157a332

Tx prefix hash: 53f542b5efcbdc51a2e477ec5e5ed8f5aa5b84daaf0ed4edb0391b68b8fedb2b
Tx public key: 3b3eeab3a70b8b0a381f8b925c56126e69b5b4f2d0647119ef6f0de9d71d716e
Timestamp: 1742990115 Timestamp [UCT]: 2025-03-26 11:55:15 Age [y:d:h:m:s]: 00:238:18:57:24
Block: 1247657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168409 RingCT/type: yes/0
Extra: 013b3eeab3a70b8b0a381f8b925c56126e69b5b4f2d0647119ef6f0de9d71d716e021100000006d2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d69c05018a1bcb1e975e47b10e5b6724815f1eccabecf26b571e7e12ccf5a7c4 0.600000000000 1734684 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": 1247667, "vin": [ { "gen": { "height": 1247657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d69c05018a1bcb1e975e47b10e5b6724815f1eccabecf26b571e7e12ccf5a7c4" } } ], "extra": [ 1, 59, 62, 234, 179, 167, 11, 139, 10, 56, 31, 139, 146, 92, 86, 18, 110, 105, 181, 180, 242, 208, 100, 113, 25, 239, 111, 13, 233, 215, 29, 113, 110, 2, 17, 0, 0, 0, 6, 210, 228, 14, 253, 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