Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f33561d1e87485d04e035718b53be3f5b15bc88b2cdb6afa9d7b68f3ad9c96

Tx prefix hash: 1880403ebec991f99fe1064b6918d9404d0a9a05159981b466c81845df37b74a
Tx public key: 0387945890d7f32ea69ebb4b442d6c8a9fece8b065388f27d7040752b3cbbe0d
Timestamp: 1733265808 Timestamp [UCT]: 2024-12-03 22:43:28 Age [y:d:h:m:s]: 00:110:15:35:21
Block: 1167436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78875 RingCT/type: yes/0
Extra: 010387945890d7f32ea69ebb4b442d6c8a9fece8b065388f27d7040752b3cbbe0d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33b412c875a54872d476a173067db60f6835d02f7987cfd5ff293ae740d4d853 0.600000000000 1653131 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": 1167446, "vin": [ { "gen": { "height": 1167436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33b412c875a54872d476a173067db60f6835d02f7987cfd5ff293ae740d4d853" } } ], "extra": [ 1, 3, 135, 148, 88, 144, 215, 243, 46, 166, 158, 187, 75, 68, 45, 108, 138, 159, 236, 232, 176, 101, 56, 143, 39, 215, 4, 7, 82, 179, 203, 190, 13, 2, 17, 0, 0, 0, 3, 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