Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fadf9bd4981e1f7f3582eb0bb99921bb857037004403747ced53d3f576e65e9e

Tx prefix hash: e2ee358765d0dae2ab3d10db6e1cef90dd3fb4ddc6e94b387137b17d785f62a1
Tx public key: bffc436a56e5eb7083f7923b0d40e096eb7292fa4ae0de8fdc6734fc7bde0294
Timestamp: 1703057366 Timestamp [UCT]: 2023-12-20 07:29:26 Age [y:d:h:m:s]: 01:112:18:14:42
Block: 917092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341719 RingCT/type: yes/0
Extra: 01bffc436a56e5eb7083f7923b0d40e096eb7292fa4ae0de8fdc6734fc7bde029402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 846d82950748b7e3dfd60f6af78aeb34ebf46acdbb2b6611e8714728f35cbe58 0.600000000000 1374656 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": 917102, "vin": [ { "gen": { "height": 917092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "846d82950748b7e3dfd60f6af78aeb34ebf46acdbb2b6611e8714728f35cbe58" } } ], "extra": [ 1, 191, 252, 67, 106, 86, 229, 235, 112, 131, 247, 146, 59, 13, 64, 224, 150, 235, 114, 146, 250, 74, 224, 222, 143, 220, 103, 52, 252, 123, 222, 2, 148, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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