Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dabfb9e398065f4b91c9849de29fa7d607d6dd710a70e56f31be6f3fce1f3b64

Tx prefix hash: c0df9443d4726410f7922d411716e35073f89b3f6a6771de4d40c8737e8d4eb8
Tx public key: 4cd0d1724ce9c8f62a722c96536a1cbd02c30907732c09146fd18194e9078ed9
Timestamp: 1713339431 Timestamp [UCT]: 2024-04-17 07:37:11 Age [y:d:h:m:s]: 00:212:03:00:33
Block: 1002330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151862 RingCT/type: yes/0
Extra: 014cd0d1724ce9c8f62a722c96536a1cbd02c30907732c09146fd18194e9078ed902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c98bfc9b0dcc5aca782642bd09b00ba639e83cefbbb3b412507e4c5f35533045 0.600000000000 1462846 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": 1002340, "vin": [ { "gen": { "height": 1002330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c98bfc9b0dcc5aca782642bd09b00ba639e83cefbbb3b412507e4c5f35533045" } } ], "extra": [ 1, 76, 208, 209, 114, 76, 233, 200, 246, 42, 114, 44, 150, 83, 106, 28, 189, 2, 195, 9, 7, 115, 44, 9, 20, 111, 209, 129, 148, 233, 7, 142, 217, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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