Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6fcfebd6656b38a3ac2d78676aa5cceeb92373c2df340db5c2d00d16a68a3c0

Tx prefix hash: 85f5e113d5731b5d86303a1e2efcda48838c97d100ee03573eaf31996456c5e1
Tx public key: 0be93fdbb8f439447b6a8a9afc4552c66264ff7662d4f3e64862df66b37ff3d2
Timestamp: 1720902752 Timestamp [UCT]: 2024-07-13 20:32:32 Age [y:d:h:m:s]: 00:315:17:07:17
Block: 1065048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225606 RingCT/type: yes/0
Extra: 010be93fdbb8f439447b6a8a9afc4552c66264ff7662d4f3e64862df66b37ff3d202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b05c5317a9c29943d7ca146b828127a9a0aef5d17346156a6294612984cfff1b 0.600000000000 1535591 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": 1065058, "vin": [ { "gen": { "height": 1065048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b05c5317a9c29943d7ca146b828127a9a0aef5d17346156a6294612984cfff1b" } } ], "extra": [ 1, 11, 233, 63, 219, 184, 244, 57, 68, 123, 106, 138, 154, 252, 69, 82, 198, 98, 100, 255, 118, 98, 212, 243, 230, 72, 98, 223, 102, 179, 127, 243, 210, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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