Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad373cd45ba2f980b7020c3cbdc1c0c15dcffaa135a812fcd1ce7799a2a593b

Tx prefix hash: d7fae93b8290d0b463e4607d6befc61e648acdf78bd32645103b5477dcc38a6d
Tx public key: abd146a0d5f31811bd752c2543a4bd66bd8bc7a7d42c3aec72eb8b877933876a
Timestamp: 1684761170 Timestamp [UCT]: 2023-05-22 13:12:50 Age [y:d:h:m:s]: 01:323:14:12:55
Block: 765672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492476 RingCT/type: yes/0
Extra: 01abd146a0d5f31811bd752c2543a4bd66bd8bc7a7d42c3aec72eb8b877933876a021100000001b3164c24000000000000000000

1 output(s) for total of 1.782423907000 dcy

stealth address amount amount idx
00: 28f813b87146bf9c65c67d66d188a34eca8527d609cd85e5011b35cfed399648 1.782423907000 1214669 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": 765682, "vin": [ { "gen": { "height": 765672 } } ], "vout": [ { "amount": 1782423907, "target": { "key": "28f813b87146bf9c65c67d66d188a34eca8527d609cd85e5011b35cfed399648" } } ], "extra": [ 1, 171, 209, 70, 160, 213, 243, 24, 17, 189, 117, 44, 37, 67, 164, 189, 102, 189, 139, 199, 167, 212, 44, 58, 236, 114, 235, 139, 135, 121, 51, 135, 106, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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