Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d00e678996ae2831dfcd3a116461fa6863ed70ae61ae4209c0633e84933868fe

Tx prefix hash: c88369d761791b2b2c94f7f5dc5df62571d7f6a6be8e41c966072f01233f61b6
Tx public key: 126d1c15b4e375784692943d9c3ff77020218e73d7bd051ea36157e8bf957832
Timestamp: 1765221659 Timestamp [UTC]: 2025-12-08 19:20:59 Age [y:d:h:m:s]: 00:348:21:02:24
Block: 1429333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254161 RingCT/type: yes/0
Extra: 01126d1c15b4e375784692943d9c3ff77020218e73d7bd051ea36157e8bf957832021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b7f18eb12a8fec209a88e4900f691192e7a66c09b291fa4e14aa39048d400b49 0.000600000000 1918058 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 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": 1429343, "vin": [ { "gen": { "height": 1429333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f18eb12a8fec209a88e4900f691192e7a66c09b291fa4e14aa39048d400b49" } } ], "extra": [ 1, 18, 109, 28, 21, 180, 227, 117, 120, 70, 146, 148, 61, 156, 63, 247, 112, 32, 33, 142, 115, 215, 189, 5, 30, 163, 97, 87, 232, 191, 149, 120, 50, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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: