Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4d581a02e7b3988261b9f3503e98f85cc5b8c1140ef5377443e40b980317df

Tx prefix hash: f013f00078fbb3fc93a8ae98c3a3d62dab0ff8e414e3b84616ad4689c1f887a5
Tx public key: f5f99aa935c3e6ec81aecf57a1fb9de1010ca8e856244ef5c5a70f5962f10050
Timestamp: 1746329073 Timestamp [UCT]: 2025-05-04 03:24:33 Age [y:d:h:m:s]: 00:200:03:26:21
Block: 1275309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140757 RingCT/type: yes/0
Extra: 01f5f99aa935c3e6ec81aecf57a1fb9de1010ca8e856244ef5c5a70f5962f100500211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4a4e0d7dba8cd2829ae4049782ad0050021e08084be4ec0a89cae3b6b21a5d0 0.600000000000 1762616 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": 1275319, "vin": [ { "gen": { "height": 1275309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4a4e0d7dba8cd2829ae4049782ad0050021e08084be4ec0a89cae3b6b21a5d0" } } ], "extra": [ 1, 245, 249, 154, 169, 53, 195, 230, 236, 129, 174, 207, 87, 161, 251, 157, 225, 1, 12, 168, 232, 86, 36, 78, 245, 197, 167, 15, 89, 98, 241, 0, 80, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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