Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5694ab185c82d723738c426eb9f65766704c4a4abd7a4a15292a5621fe76b24

Tx prefix hash: 59b8ab2c788656066fdd1a16fc1b740d345ce6175278cb24fb498a9e7c14e70b
Tx public key: 7dc57dd1e7d0c16b78779bcdfee60932d00c187a9d936a3c778fed81fbc65232
Timestamp: 1696881730 Timestamp [UCT]: 2023-10-09 20:02:10 Age [y:d:h:m:s]: 01:200:21:15:00
Block: 866103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404622 RingCT/type: yes/0
Extra: 017dc57dd1e7d0c16b78779bcdfee60932d00c187a9d936a3c778fed81fbc6523202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.828402227000 dcy

stealth address amount amount idx
00: 69a877f07c120c0bdd63295d019cb0be14916224446fc4481a86dfab4aa01fe7 0.828402227000 1320671 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": 866113, "vin": [ { "gen": { "height": 866103 } } ], "vout": [ { "amount": 828402227, "target": { "key": "69a877f07c120c0bdd63295d019cb0be14916224446fc4481a86dfab4aa01fe7" } } ], "extra": [ 1, 125, 197, 125, 209, 231, 208, 193, 107, 120, 119, 155, 205, 254, 230, 9, 50, 208, 12, 24, 122, 157, 147, 106, 60, 119, 143, 237, 129, 251, 198, 82, 50, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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