Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c08913574e7aa291ffa2f25b47d2eb9be691e477f3bf77e919b3e607eb2870

Tx prefix hash: 7ec83294450a0f0922badf0f10b098c40f9179ee66007c1c3d8f8e2e76b0c925
Tx public key: f29addff6dcedc3c30928016218ed5d35a6b5638b60d0d913057ceed24fcb0c4
Timestamp: 1733100621 Timestamp [UCT]: 2024-12-02 00:50:21 Age [y:d:h:m:s]: 00:117:05:57:49
Block: 1166067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83595 RingCT/type: yes/0
Extra: 01f29addff6dcedc3c30928016218ed5d35a6b5638b60d0d913057ceed24fcb0c4021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae8085d6d8f2eaab732fa733be03fba845c1f5c8b60413fd3ad70ea7257d7220 0.600000000000 1651744 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": 1166077, "vin": [ { "gen": { "height": 1166067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae8085d6d8f2eaab732fa733be03fba845c1f5c8b60413fd3ad70ea7257d7220" } } ], "extra": [ 1, 242, 154, 221, 255, 109, 206, 220, 60, 48, 146, 128, 22, 33, 142, 213, 211, 90, 107, 86, 56, 182, 13, 13, 145, 48, 87, 206, 237, 36, 252, 176, 196, 2, 17, 0, 0, 0, 7, 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