Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f27bd2a0542bb3e39cb8a008419fcac6430ab50e89015fd268d8230febd90be

Tx prefix hash: 0e04949afca9bc20e7e5fb38203e43be04f3589c2571713c593b0a5b9e9f8fb1
Tx public key: ba6cfc5c654fef12444ee6e9333d9a78ffb0bcb9d5569e56ca5aff36f23f04dd
Timestamp: 1664835556 Timestamp [UCT]: 2022-10-03 22:19:16 Age [y:d:h:m:s]: 02:189:06:02:23
Block: 601339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656837 RingCT/type: yes/0
Extra: 01ba6cfc5c654fef12444ee6e9333d9a78ffb0bcb9d5569e56ca5aff36f23f04dd02110000000375e3f0e9000000000000000000

1 output(s) for total of 6.244739452000 dcy

stealth address amount amount idx
00: b5033d92520d6fa46161b13e9ef97d6351b7711b380035ff30d8ab5116868760 6.244739452000 1037370 of 0

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": 601349, "vin": [ { "gen": { "height": 601339 } } ], "vout": [ { "amount": 6244739452, "target": { "key": "b5033d92520d6fa46161b13e9ef97d6351b7711b380035ff30d8ab5116868760" } } ], "extra": [ 1, 186, 108, 252, 92, 101, 79, 239, 18, 68, 78, 230, 233, 51, 61, 154, 120, 255, 176, 188, 185, 213, 86, 158, 86, 202, 90, 255, 54, 242, 63, 4, 221, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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