Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c52fcb2144682521d046cfb67a54a5638de4206fc86488044135461b0d01c57d

Tx prefix hash: bf78f8f267bc2f6131d54d1ef1301d297009d8711c0a098cc0a02987fd50824a
Tx public key: e8d5a2c74748f1c13546238627ad08b2f2d7ea17f3e9ff3f7d3b035968fe0603
Timestamp: 1702835066 Timestamp [UCT]: 2023-12-17 17:44:26 Age [y:d:h:m:s]: 01:114:04:44:59
Block: 915246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342744 RingCT/type: yes/0
Extra: 01e8d5a2c74748f1c13546238627ad08b2f2d7ea17f3e9ff3f7d3b035968fe0603021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cd1d7fffa8d6361853c287dac670ed0e4d0e84cc76f43e838c173624870177e 0.600000000000 1372636 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": 915256, "vin": [ { "gen": { "height": 915246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cd1d7fffa8d6361853c287dac670ed0e4d0e84cc76f43e838c173624870177e" } } ], "extra": [ 1, 232, 213, 162, 199, 71, 72, 241, 193, 53, 70, 35, 134, 39, 173, 8, 178, 242, 215, 234, 23, 243, 233, 255, 63, 125, 59, 3, 89, 104, 254, 6, 3, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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