Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d325f840ef1f31f91ccd698991f8e4d64cf162be7ef9824c60b144a39f5b2ac0

Tx prefix hash: dd994352d3b9dba66dfa1bf2dd4d8fe02df8e6da410ce757aaf5023c3a961e68
Tx public key: e6934fd0f8a4dd4d61d21b4622a4cb984f3223d9379f133d2cbdf28d752a8dab
Timestamp: 1648343926 Timestamp [UCT]: 2022-03-27 01:18:46 Age [y:d:h:m:s]: 02:273:16:46:33
Block: 467157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715175 RingCT/type: yes/0
Extra: 01e6934fd0f8a4dd4d61d21b4622a4cb984f3223d9379f133d2cbdf28d752a8dab021100000009d3fcec30000000000000000000

1 output(s) for total of 17.382618012000 dcy

stealth address amount amount idx
00: a1938a96ab6afb1399b192b404d5fae886b4021bc310c749771dccd36eee76e5 17.382618012000 885608 of 0

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": 467167, "vin": [ { "gen": { "height": 467157 } } ], "vout": [ { "amount": 17382618012, "target": { "key": "a1938a96ab6afb1399b192b404d5fae886b4021bc310c749771dccd36eee76e5" } } ], "extra": [ 1, 230, 147, 79, 208, 248, 164, 221, 77, 97, 210, 27, 70, 34, 164, 203, 152, 79, 50, 35, 217, 55, 159, 19, 61, 44, 189, 242, 141, 117, 42, 141, 171, 2, 17, 0, 0, 0, 9, 211, 252, 236, 48, 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