Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd65a9978e1087496ef0f125321fa39a96f4086024b715cdc316bf3017cc46dc

Tx prefix hash: e3261217001c2a63f9dd5ebb5d2474d34bec39c71d118d44e81cb7d2e73918a1
Tx public key: 62523b4d587ccad2ffd1fcf9d8970b5ff03ba2d7eb7ec794237c8801d4c43397
Timestamp: 1700045874 Timestamp [UCT]: 2023-11-15 10:57:54 Age [y:d:h:m:s]: 01:360:09:16:13
Block: 892125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516477 RingCT/type: yes/0
Extra: 0162523b4d587ccad2ffd1fcf9d8970b5ff03ba2d7eb7ec794237c8801d4c43397021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.679234179000 dcy

stealth address amount amount idx
00: ad6238b6c9a8565e07c483c59907ca0ba941c041274066b5b86c240c6885288c 0.679234179000 1348190 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": 892135, "vin": [ { "gen": { "height": 892125 } } ], "vout": [ { "amount": 679234179, "target": { "key": "ad6238b6c9a8565e07c483c59907ca0ba941c041274066b5b86c240c6885288c" } } ], "extra": [ 1, 98, 82, 59, 77, 88, 124, 202, 210, 255, 209, 252, 249, 216, 151, 11, 95, 240, 59, 162, 215, 235, 126, 199, 148, 35, 124, 136, 1, 212, 196, 51, 151, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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