Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94fa3983472cc931701cfc68441abe05d5ce71db7e9e7529feb9847511a0a632

Tx prefix hash: bd958874a60628d3aa08b9ea117453eafaecfb33f018b9505325b335cd887d5f
Tx public key: b589ff00b7b65e6e9203b5e5f1bcf89fda2d942b22ba160ab68d083c2ba4b8f8
Timestamp: 1709315824 Timestamp [UCT]: 2024-03-01 17:57:04 Age [y:d:h:m:s]: 01:027:03:55:10
Block: 968992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280402 RingCT/type: yes/0
Extra: 01b589ff00b7b65e6e9203b5e5f1bcf89fda2d942b22ba160ab68d083c2ba4b8f802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae105e88ddeb5595efff33d63a15296df9327eaba6e7251e71082c9cabaf2fbc 0.600000000000 1428819 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": 969002, "vin": [ { "gen": { "height": 968992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae105e88ddeb5595efff33d63a15296df9327eaba6e7251e71082c9cabaf2fbc" } } ], "extra": [ 1, 181, 137, 255, 0, 183, 182, 94, 110, 146, 3, 181, 229, 241, 188, 248, 159, 218, 45, 148, 43, 34, 186, 22, 10, 182, 141, 8, 60, 43, 164, 184, 248, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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