Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d07183afd0a715d3dba0d7b353656838073f159f6484ea64f50e8a41b377da6

Tx prefix hash: 558d56e0dfd2ee1bb0136648879cf88b7bb219a51c2028939ebf26cf99ed6cea
Tx public key: 06e6baf92cba8ceb9057f94c07a687fb065c247c22d9429f33c44dce44f8a8e2
Timestamp: 1735841364 Timestamp [UCT]: 2025-01-02 18:09:24 Age [y:d:h:m:s]: 00:168:06:32:02
Block: 1188754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119959 RingCT/type: yes/0
Extra: 0106e6baf92cba8ceb9057f94c07a687fb065c247c22d9429f33c44dce44f8a8e202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2bb090555960a7a3aa89bd173dc06d845026cb9cf8d3846b96eb9728499c72d 0.600000000000 1675257 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": 1188764, "vin": [ { "gen": { "height": 1188754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2bb090555960a7a3aa89bd173dc06d845026cb9cf8d3846b96eb9728499c72d" } } ], "extra": [ 1, 6, 230, 186, 249, 44, 186, 140, 235, 144, 87, 249, 76, 7, 166, 135, 251, 6, 92, 36, 124, 34, 217, 66, 159, 51, 196, 77, 206, 68, 248, 168, 226, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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