Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a21b41cba500bf80c66d74ce7cb8403cf4a38bef9a3e214ba275c1d42071ebba

Tx prefix hash: 919ebe6718a3c09cfb017313a763daeb0775e4d595d30a8d30d70add1b30bbbd
Tx public key: 191a4a4901e7b2b13d60e8778fd6299165ec4dbb66aef9c77ccf204bef9f155e
Timestamp: 1725548657 Timestamp [UCT]: 2024-09-05 15:04:17 Age [y:d:h:m:s]: 00:214:15:10:45
Block: 1103559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153229 RingCT/type: yes/0
Extra: 01191a4a4901e7b2b13d60e8778fd6299165ec4dbb66aef9c77ccf204bef9f155e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2790a4e089fb51f037ee6b85a879523c808373034c5903edb00312121262f4f2 0.600000000000 1580436 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": 1103569, "vin": [ { "gen": { "height": 1103559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2790a4e089fb51f037ee6b85a879523c808373034c5903edb00312121262f4f2" } } ], "extra": [ 1, 25, 26, 74, 73, 1, 231, 178, 177, 61, 96, 232, 119, 143, 214, 41, 145, 101, 236, 77, 187, 102, 174, 249, 199, 124, 207, 32, 75, 239, 159, 21, 94, 2, 17, 0, 0, 0, 2, 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