Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9739b701b12bc617b71f9bc709bdadb0f64b9b7c0e41eab37f115a1bd323de8d

Tx prefix hash: 67301ab3e030b20fe852fc325db1112dbb4d72f5f63f3576762fabe3761b118b
Tx public key: ae83b62f5c51f60fcd79aa00917328c9e5c506813b2c8ec653a67926ca8592c9
Timestamp: 1721555916 Timestamp [UCT]: 2024-07-21 09:58:36 Age [y:d:h:m:s]: 00:245:08:57:05
Block: 1070444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175288 RingCT/type: yes/0
Extra: 01ae83b62f5c51f60fcd79aa00917328c9e5c506813b2c8ec653a67926ca8592c9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e94853f3488f1431cda1f3e02a4a8f4d4200fb897ea9f1f1510a884ea71d20ac 0.600000000000 1542281 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": 1070454, "vin": [ { "gen": { "height": 1070444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e94853f3488f1431cda1f3e02a4a8f4d4200fb897ea9f1f1510a884ea71d20ac" } } ], "extra": [ 1, 174, 131, 182, 47, 92, 81, 246, 15, 205, 121, 170, 0, 145, 115, 40, 201, 229, 197, 6, 129, 59, 44, 142, 198, 83, 166, 121, 38, 202, 133, 146, 201, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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