Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 888dfb75b0d19bfb1980742286908d82736e1c74d66860f537c12a464a0ff251

Tx prefix hash: cb3b62e90f61703229407a2fe1a03423f8439163c9802d167407385c5537e2ea
Tx public key: 3dca42ea875a490c9a6cec1391dd902f92b31ef5726c27a5746f1194a15530be
Timestamp: 1694043848 Timestamp [UCT]: 2023-09-06 23:44:08 Age [y:d:h:m:s]: 01:208:15:58:45
Block: 842538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410255 RingCT/type: yes/0
Extra: 013dca42ea875a490c9a6cec1391dd902f92b31ef5726c27a5746f1194a15530be02110000000f4b8f5122000000000000000000

1 output(s) for total of 0.991566668000 dcy

stealth address amount amount idx
00: cc7d69e49f24371ce2b603a7095ab847366848cf993bbff3d4c5252d8d6ad3f7 0.991566668000 1295668 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": 842548, "vin": [ { "gen": { "height": 842538 } } ], "vout": [ { "amount": 991566668, "target": { "key": "cc7d69e49f24371ce2b603a7095ab847366848cf993bbff3d4c5252d8d6ad3f7" } } ], "extra": [ 1, 61, 202, 66, 234, 135, 90, 73, 12, 154, 108, 236, 19, 145, 221, 144, 47, 146, 179, 30, 245, 114, 108, 39, 165, 116, 111, 17, 148, 161, 85, 48, 190, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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