Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf2496fec2ee2ecbb1dd6647de39dd6115c0d4efbf9f750d1d955b7b2cf8405

Tx prefix hash: db21ed1bac659b56b7e0a692d5819813bd10936bd1239f9e73c6b7f8a02622d5
Tx public key: cc1d7fc4fa8138fe98a20c56604bc2ee3dceeb5785eecc61b0cc4fff9aaf00f8
Timestamp: 1701538230 Timestamp [UCT]: 2023-12-02 17:30:30 Age [y:d:h:m:s]: 01:082:22:31:30
Block: 904494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320389 RingCT/type: yes/0
Extra: 01cc1d7fc4fa8138fe98a20c56604bc2ee3dceeb5785eecc61b0cc4fff9aaf00f8021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.618067463000 dcy

stealth address amount amount idx
00: 28ff9f34016cdf628fced7ffce83e708f273991e8add37abd86f654022ef17d6 0.618067463000 1361253 of 0

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": 904504, "vin": [ { "gen": { "height": 904494 } } ], "vout": [ { "amount": 618067463, "target": { "key": "28ff9f34016cdf628fced7ffce83e708f273991e8add37abd86f654022ef17d6" } } ], "extra": [ 1, 204, 29, 127, 196, 250, 129, 56, 254, 152, 162, 12, 86, 96, 75, 194, 238, 61, 206, 235, 87, 133, 238, 204, 97, 176, 204, 79, 255, 154, 175, 0, 248, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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