Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d2512bdcb1653b60b0ffb9cfb654c3d3837c7c3b799a5b6cb5cfc995295ecd

Tx prefix hash: 4ac922639185d92e1755bdb97477f0d0c1ab11c1d550d4dc5bde8b4d2f2b9642
Tx public key: 11665a4c5f51da475ac24fa1945450ac4e09a35ced3df8b524e5f1e4bc989f2c
Timestamp: 1734978387 Timestamp [UCT]: 2024-12-23 18:26:27 Age [y:d:h:m:s]: 00:104:01:34:36
Block: 1181638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74128 RingCT/type: yes/0
Extra: 0111665a4c5f51da475ac24fa1945450ac4e09a35ced3df8b524e5f1e4bc989f2c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdbed33b3fdd5640ed251b6fd9e1a5e5aefe88fcbca315cdc9ae1e5829cf61d4 0.600000000000 1668063 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": 1181648, "vin": [ { "gen": { "height": 1181638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdbed33b3fdd5640ed251b6fd9e1a5e5aefe88fcbca315cdc9ae1e5829cf61d4" } } ], "extra": [ 1, 17, 102, 90, 76, 95, 81, 218, 71, 90, 194, 79, 161, 148, 84, 80, 172, 78, 9, 163, 92, 237, 61, 248, 181, 36, 229, 241, 228, 188, 152, 159, 44, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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