Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 816eeaa19e16aa80baa6768edbf96791d2cd7d095acd3c39f9d1a1ebdc5cbaf3

Tx prefix hash: 77f2a0e8c3157b221162cfb18a89d720d3cafbb50ca889d76ea416ec6d879909
Tx public key: 8178647be9d7244ee5a9e57fdeef884eabe139d5bba0df267d55d9702ba0cbf9
Timestamp: 1743705640 Timestamp [UTC]: 2025-04-03 18:40:40 Age [y:d:h:m:s]: 01:229:13:41:31
Block: 1253581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428170 RingCT/type: yes/0
Extra: 018178647be9d7244ee5a9e57fdeef884eabe139d5bba0df267d55d9702ba0cbf90211000000024060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dffd0566733a6814ed13fccd3ebf1ed3f03ae91ceed45bce735e9c597696f76b 0.000600000000 1740662 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": 1253591, "vin": [ { "gen": { "height": 1253581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dffd0566733a6814ed13fccd3ebf1ed3f03ae91ceed45bce735e9c597696f76b" } } ], "extra": [ 1, 129, 120, 100, 123, 233, 215, 36, 78, 229, 169, 229, 127, 222, 239, 136, 78, 171, 225, 57, 213, 187, 160, 223, 38, 125, 85, 217, 112, 43, 160, 203, 249, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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: