Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5c23b6da70215634ce846696c3af3a306d22ec425b693ee8539ecd57c64211

Tx prefix hash: d1becb0bd08082515b3ae22474e38cc87cffb0a494d89238ef51224065512b9c
Tx public key: cb06b9e1df9cd8e88f049496837d7a60f14b4d0cfd87faa8f2d21fc023a4202e
Timestamp: 1699546370 Timestamp [UCT]: 2023-11-09 16:12:50 Age [y:d:h:m:s]: 02:001:05:51:37
Block: 887994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520663 RingCT/type: yes/0
Extra: 01cb06b9e1df9cd8e88f049496837d7a60f14b4d0cfd87faa8f2d21fc023a4202e0211000000044b8f5122000000000000000000

1 output(s) for total of 0.700982628000 dcy

stealth address amount amount idx
00: e3ecf9a7b0bcec5e71d9e62946febd4e48ce3ee338967ef6eb71d0d2c4da92a1 0.700982628000 1343911 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": 888004, "vin": [ { "gen": { "height": 887994 } } ], "vout": [ { "amount": 700982628, "target": { "key": "e3ecf9a7b0bcec5e71d9e62946febd4e48ce3ee338967ef6eb71d0d2c4da92a1" } } ], "extra": [ 1, 203, 6, 185, 225, 223, 156, 216, 232, 143, 4, 148, 150, 131, 125, 122, 96, 241, 75, 77, 12, 253, 135, 250, 168, 242, 210, 31, 192, 35, 164, 32, 46, 2, 17, 0, 0, 0, 4, 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