Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df41bb7c801f37e625de2a009f1235a5193edf975f3e4b9696d891b24761a8df

Tx prefix hash: a03f29411c6b1f09c61601bc59a27c9d3bd1fd91b4b73f53902b7125c58a4ec8
Tx public key: 2045d4a600e8e329443b7f7dd28d100669c5b841870ac0e93ae63c8cca16e0fe
Timestamp: 1579352337 Timestamp [UTC]: 2020-01-18 12:58:57 Age [y:d:h:m:s]: 06:307:14:57:26
Block: 48318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1634061 RingCT/type: yes/0
Extra: 012045d4a600e8e329443b7f7dd28d100669c5b841870ac0e93ae63c8cca16e0fe021100000001bd0f9f9f000000000000000000

1 output(s) for total of 0.424524973646 xmr

stealth address amount amount idx tag
00: c16ddd13486808df38c2dc96535500b14bad5afc022c51777955500d54e72e46 0.424524973646 89483 of 0 -

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 dinastycoin-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": 48328, "vin": [ { "gen": { "height": 48318 } } ], "vout": [ { "amount": 424524973646, "target": { "key": "c16ddd13486808df38c2dc96535500b14bad5afc022c51777955500d54e72e46" } } ], "extra": [ 1, 32, 69, 212, 166, 0, 232, 227, 41, 68, 59, 127, 125, 210, 141, 16, 6, 105, 197, 184, 65, 135, 10, 192, 233, 58, 230, 60, 140, 202, 22, 224, 254, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: