Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c910ca269b29646e072caf374bfea2ea0cea711be182a2ff713baf8bcb7d2553

Tx prefix hash: d22ce038208ddeedf49a9b7ef404496ecd690ab70a9e0390c9b9793dae519b19
Tx public key: 0f8f214cd32f00b009db13dfe623be87e7af42a7bbb9238d7d5c2a2ec5efb5e9
Timestamp: 1729481723 Timestamp [UCT]: 2024-10-21 03:35:23 Age [y:d:h:m:s]: 00:216:00:22:05
Block: 1136129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154230 RingCT/type: yes/0
Extra: 010f8f214cd32f00b009db13dfe623be87e7af42a7bbb9238d7d5c2a2ec5efb5e9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58f21dbbd1af4d7b3fb22d894042bfea13e7bf9e4f093ccbb2e13a9ab76f77e7 0.600000000000 1619472 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": 1136139, "vin": [ { "gen": { "height": 1136129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58f21dbbd1af4d7b3fb22d894042bfea13e7bf9e4f093ccbb2e13a9ab76f77e7" } } ], "extra": [ 1, 15, 143, 33, 76, 211, 47, 0, 176, 9, 219, 19, 223, 230, 35, 190, 135, 231, 175, 66, 167, 187, 185, 35, 141, 125, 92, 42, 46, 197, 239, 181, 233, 2, 17, 0, 0, 0, 1, 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