Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f2a45e1fcab79787ad54cb4155d72eeb3b7d8532402f1cbbb55b6f64e5b800d

Tx prefix hash: 12245f194e88820131189f52710dca2066113e2599a6219bf4f245c7cc6fd22f
Tx public key: bb37f11fe60c88b557df7894b78f70eb294a9a7fe999d110d4acdbc5014f4a8b
Timestamp: 1723136990 Timestamp [UCT]: 2024-08-08 17:09:50 Age [y:d:h:m:s]: 01:016:02:36:42
Block: 1083556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270075 RingCT/type: yes/0
Extra: 01bb37f11fe60c88b557df7894b78f70eb294a9a7fe999d110d4acdbc5014f4a8b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e17117f195f09b00535f11a36f4981bbbee25b107cb673f5e95689860b9aa6 0.600000000000 1557523 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": 1083566, "vin": [ { "gen": { "height": 1083556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e17117f195f09b00535f11a36f4981bbbee25b107cb673f5e95689860b9aa6" } } ], "extra": [ 1, 187, 55, 241, 31, 230, 12, 136, 181, 87, 223, 120, 148, 183, 143, 112, 235, 41, 74, 154, 127, 233, 153, 209, 16, 212, 172, 219, 197, 1, 79, 74, 139, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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