Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9334922c44d7519366e26e218f1b7d4064dfc67516d294328c0576273b3c4da3

Tx prefix hash: 2d0fcb69d0b1ef58d93fa81e42166509834a970cd78c7fedb5fb1c2c0ea104ac
Tx public key: c64d18ad1ddd3ff0aafcd410e2117ef2a4d121569439346505f28cf946e5c8e8
Timestamp: 1675460353 Timestamp [UCT]: 2023-02-03 21:39:13 Age [y:d:h:m:s]: 02:062:13:23:28
Block: 689176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566334 RingCT/type: yes/0
Extra: 01c64d18ad1ddd3ff0aafcd410e2117ef2a4d121569439346505f28cf946e5c8e802110000000133af99f4000000000000000000

1 output(s) for total of 3.195021247000 dcy

stealth address amount amount idx
00: 314e0518bebc84bbb2d8ad2efaa81d315543e9d93ce52be43281f53d1a2d8615 3.195021247000 1131840 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": 689186, "vin": [ { "gen": { "height": 689176 } } ], "vout": [ { "amount": 3195021247, "target": { "key": "314e0518bebc84bbb2d8ad2efaa81d315543e9d93ce52be43281f53d1a2d8615" } } ], "extra": [ 1, 198, 77, 24, 173, 29, 221, 63, 240, 170, 252, 212, 16, 226, 17, 126, 242, 164, 209, 33, 86, 148, 57, 52, 101, 5, 242, 140, 249, 70, 229, 200, 232, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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