Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d66ca8825bd5b11686b6c5f22a6f4ab8d5a80766166541167539a1bd2dbde666

Tx prefix hash: 54f368afcceadbb6065116adab6888fdcd440c5d3c62d645e8805b10e78385b9
Tx public key: 64d0dbc6c7a6f1e7e8fd9da26190918119b93d42ffe6e0827dbfc1db25c3d2b7
Timestamp: 1699950763 Timestamp [UCT]: 2023-11-14 08:32:43 Age [y:d:h:m:s]: 01:064:04:28:43
Block: 891341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307282 RingCT/type: yes/0
Extra: 0164d0dbc6c7a6f1e7e8fd9da26190918119b93d42ffe6e0827dbfc1db25c3d2b702110000000775e3f0e9000000000000000000

1 output(s) for total of 0.683309171000 dcy

stealth address amount amount idx
00: bb3b304a63c1253f28e0aee78d8cae3bfc5654ad0b262b85c2d256d83ee23ed2 0.683309171000 1347380 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": 891351, "vin": [ { "gen": { "height": 891341 } } ], "vout": [ { "amount": 683309171, "target": { "key": "bb3b304a63c1253f28e0aee78d8cae3bfc5654ad0b262b85c2d256d83ee23ed2" } } ], "extra": [ 1, 100, 208, 219, 198, 199, 166, 241, 231, 232, 253, 157, 162, 97, 144, 145, 129, 25, 185, 61, 66, 255, 230, 224, 130, 125, 191, 193, 219, 37, 195, 210, 183, 2, 17, 0, 0, 0, 7, 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