Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944af968ebb4ac250fdd348990f4aa32f22bd05df7b59e2d452b97a3e8b8d209

Tx prefix hash: 19ca821ec9bc789889cfc9a31c970988d8d3688db6284e9f8820a5ab8dbfde7a
Tx public key: 45053fb37c881004a64478c1f9a5bde4d0418df802813b9514c547efe08f9bd2
Timestamp: 1762491425 Timestamp [UCT]: 2025-11-07 04:57:05 Age [y:d:h:m:s]: 00:080:15:14:54
Block: 1406703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57558 RingCT/type: yes/0
Extra: 0145053fb37c881004a64478c1f9a5bde4d0418df802813b9514c547efe08f9bd20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa01c766fdc6b162ff0de79dcbbbd113c3bbd403295c50b9865baf847fd94239 0.600000000000 1895092 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": 1406713, "vin": [ { "gen": { "height": 1406703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa01c766fdc6b162ff0de79dcbbbd113c3bbd403295c50b9865baf847fd94239" } } ], "extra": [ 1, 69, 5, 63, 179, 124, 136, 16, 4, 166, 68, 120, 193, 249, 165, 189, 228, 208, 65, 141, 248, 2, 129, 59, 149, 20, 197, 71, 239, 224, 143, 155, 210, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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