Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e51d60606d536af2d8e55898627011f82545339950226dce19ea989c6da977ad

Tx prefix hash: b0e4d1b04df839eefebb0be0c84c2e96fe0a6c0240720718d46ac82401621177
Tx public key: 16dcc4530b87f3c25ccd6adad52c72e6a5f7e6125dd94f1b3bdd5e084c9f7eff
Timestamp: 1733583315 Timestamp [UCT]: 2024-12-07 14:55:15 Age [y:d:h:m:s]: 00:116:02:10:39
Block: 1170068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82761 RingCT/type: yes/0
Extra: 0116dcc4530b87f3c25ccd6adad52c72e6a5f7e6125dd94f1b3bdd5e084c9f7eff021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cd6de936d4ab4a3d413ac87496be450ffffa786f423c94ca0c9356642f070af 0.600000000000 1655797 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": 1170078, "vin": [ { "gen": { "height": 1170068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cd6de936d4ab4a3d413ac87496be450ffffa786f423c94ca0c9356642f070af" } } ], "extra": [ 1, 22, 220, 196, 83, 11, 135, 243, 194, 92, 205, 106, 218, 213, 44, 114, 230, 165, 247, 230, 18, 93, 217, 79, 27, 59, 221, 94, 8, 76, 159, 126, 255, 2, 17, 0, 0, 0, 6, 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