Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c869d0e293172d2b31044394dd0e618613207c0b4a7251037ecd679e711a72a4

Tx prefix hash: b0835d1b3f32a17987d949827c68a895d7e600799e5791ae914d70d30f9e783f
Tx public key: 95cc2a840490d674b8a249a034629a5df8c0376d1f879379f2ba9542e7d55fa9
Timestamp: 1711738238 Timestamp [UCT]: 2024-03-29 18:50:38 Age [y:d:h:m:s]: 01:078:10:57:34
Block: 989082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316964 RingCT/type: yes/0
Extra: 0195cc2a840490d674b8a249a034629a5df8c0376d1f879379f2ba9542e7d55fa902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19d802f41ef1e50bdfad41255176cd147112e0d456adbf3bb06de6b991a2ad05 0.600000000000 1449377 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": 989092, "vin": [ { "gen": { "height": 989082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19d802f41ef1e50bdfad41255176cd147112e0d456adbf3bb06de6b991a2ad05" } } ], "extra": [ 1, 149, 204, 42, 132, 4, 144, 214, 116, 184, 162, 73, 160, 52, 98, 154, 93, 248, 192, 55, 109, 31, 135, 147, 121, 242, 186, 149, 66, 231, 213, 95, 169, 2, 17, 0, 0, 0, 2, 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