Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ac0b595311c741461b865b2cb5086c47614bc051d80dce01f722796417ec22b

Tx prefix hash: 2ee607c3583d62df62d7052476462818877133e90d4f5abf32f1af037f8bfad6
Tx public key: 0eb91c26138cfce088df419a5eb7fdce3777d448f9d4a7c604390abe8de1576f
Timestamp: 1750737046 Timestamp [UCT]: 2025-06-24 03:50:46 Age [y:d:h:m:s]: 00:145:00:36:10
Block: 1311558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101581 RingCT/type: yes/0
Extra: 010eb91c26138cfce088df419a5eb7fdce3777d448f9d4a7c604390abe8de1576f021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85849a61e8ae094523bdb6c317aea61f620b19238b1a3773e0ca091d9a5910d4 0.600000000000 1799185 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": 1311568, "vin": [ { "gen": { "height": 1311558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85849a61e8ae094523bdb6c317aea61f620b19238b1a3773e0ca091d9a5910d4" } } ], "extra": [ 1, 14, 185, 28, 38, 19, 140, 252, 224, 136, 223, 65, 154, 94, 183, 253, 206, 55, 119, 212, 72, 249, 212, 167, 198, 4, 57, 10, 190, 141, 225, 87, 111, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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