Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdbe89f23843a6de7bf423ee3a2e17af006112965e03f6aaaf0fae8d6da7d4e

Tx prefix hash: 32565cf291584b1092bf860fadd5f236237c63db3649750b3af74d3c570dedd2
Tx public key: d3dca36f32f38f59ec44a2315c6bb246cd18d0cccdb2bfd4cf65af668d31edb3
Timestamp: 1740766143 Timestamp [UCT]: 2025-02-28 18:09:03 Age [y:d:h:m:s]: 00:328:13:34:20
Block: 1229251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232534 RingCT/type: yes/0
Extra: 01d3dca36f32f38f59ec44a2315c6bb246cd18d0cccdb2bfd4cf65af668d31edb302110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a19a800b3ab62a0694e974a584e1bd25405c1d891f6bc7ca8cc70e4d8ec477 0.600000000000 1716136 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": 1229261, "vin": [ { "gen": { "height": 1229251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a19a800b3ab62a0694e974a584e1bd25405c1d891f6bc7ca8cc70e4d8ec477" } } ], "extra": [ 1, 211, 220, 163, 111, 50, 243, 143, 89, 236, 68, 162, 49, 92, 107, 178, 70, 205, 24, 208, 204, 205, 178, 191, 212, 207, 101, 175, 102, 141, 49, 237, 179, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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