Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 095c8f1a0ba16e889275e2b013152e041e2e22ba2c066eb4873c1e7a2d22edca

Tx prefix hash: d8ed246fd2423c0afec2086a0c2c52c86209cb5321882f776e8d07bd3fa750e4
Tx public key: 2f028cca37954ae01e2639191b8d3487aae398e10a8c3e30d9afd8ca1996ccea
Timestamp: 1711787327 Timestamp [UCT]: 2024-03-30 08:28:47 Age [y:d:h:m:s]: 01:058:10:46:00
Block: 989494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302746 RingCT/type: yes/0
Extra: 012f028cca37954ae01e2639191b8d3487aae398e10a8c3e30d9afd8ca1996ccea02110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a3dc6c67255a1777d7f135ef997901097a150d720da1b27954947167513d63 0.600000000000 1449793 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": 989504, "vin": [ { "gen": { "height": 989494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a3dc6c67255a1777d7f135ef997901097a150d720da1b27954947167513d63" } } ], "extra": [ 1, 47, 2, 140, 202, 55, 149, 74, 224, 30, 38, 57, 25, 27, 141, 52, 135, 170, 227, 152, 225, 10, 140, 62, 48, 217, 175, 216, 202, 25, 150, 204, 234, 2, 17, 0, 0, 0, 12, 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