Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95e4bedb4572905a916b9ffbd1c9d59e0de1592ca05f87bd56f9f31ee42fff96

Tx prefix hash: bc7c1e4a20bef4dd9aa1d8826374bcd0439fc6c4ffb8cac18325992a6f0df85c
Tx public key: 71ac3da6ad64d91f03e1b8894114925f22f13a889413e9de610b5a3f5edddeec
Timestamp: 1680408512 Timestamp [UCT]: 2023-04-02 04:08:32 Age [y:d:h:m:s]: 01:283:02:40:44
Block: 730220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463203 RingCT/type: yes/0
Extra: 0171ac3da6ad64d91f03e1b8894114925f22f13a889413e9de610b5a3f5edddeec0211000000015029cbac000000000000000000

1 output(s) for total of 2.336029072000 dcy

stealth address amount amount idx
00: 61b17b09f3e3beea6225f8f3b62d7a038ee7f02d28791f2f6c7cae7b64a3ec8f 2.336029072000 1175833 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": 730230, "vin": [ { "gen": { "height": 730220 } } ], "vout": [ { "amount": 2336029072, "target": { "key": "61b17b09f3e3beea6225f8f3b62d7a038ee7f02d28791f2f6c7cae7b64a3ec8f" } } ], "extra": [ 1, 113, 172, 61, 166, 173, 100, 217, 31, 3, 225, 184, 137, 65, 20, 146, 95, 34, 241, 58, 136, 148, 19, 233, 222, 97, 11, 90, 63, 94, 221, 222, 236, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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