Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b162c64250970c5a97e0a70acc5a82f30cc9e4669370c3673526ed81726d976b

Tx prefix hash: 8298b0defbbea400b19da95c348ed4ffd9b7ecbebee19d6319ae6f51c8dcc299
Tx public key: 8c09be16ee02ca1929ed280f2654af2c33ec7fb3f8f73f880e27a50215d3e0c6
Timestamp: 1736451319 Timestamp [UCT]: 2025-01-09 19:35:19 Age [y:d:h:m:s]: 00:304:14:12:08
Block: 1193796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215200 RingCT/type: yes/0
Extra: 018c09be16ee02ca1929ed280f2654af2c33ec7fb3f8f73f880e27a50215d3e0c60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e462dc045d84f3de1337272e4543e8c5cf562594336f4a2799463ba9efaf4c27 0.600000000000 1680361 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": 1193806, "vin": [ { "gen": { "height": 1193796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e462dc045d84f3de1337272e4543e8c5cf562594336f4a2799463ba9efaf4c27" } } ], "extra": [ 1, 140, 9, 190, 22, 238, 2, 202, 25, 41, 237, 40, 15, 38, 84, 175, 44, 51, 236, 127, 179, 248, 247, 63, 136, 14, 39, 165, 2, 21, 211, 224, 198, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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