Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e60f5adb34a8a54fc54ab2e69e5a028897b04e8cf4ced47df22c85424ed302d7

Tx prefix hash: 57ac858a0f609c9f447f0b8998ba7e199dcf97387ee027bbaf07402536102964
Tx public key: 9117be3750b34fa6ccbdd9e836354de87891e54db55aae61b20577127d64f5aa
Timestamp: 1744470656 Timestamp [UTC]: 2025-04-12 15:10:56 Age [y:d:h:m:s]: 01:215:21:21:59
Block: 1259924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418211 RingCT/type: yes/0
Extra: 019117be3750b34fa6ccbdd9e836354de87891e54db55aae61b20577127d64f5aa0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3e28da1e3c3f66af73765670197b417c743c04e3fdb7f47031ead783d98494f1 0.000600000000 1747075 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": 1259934, "vin": [ { "gen": { "height": 1259924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e28da1e3c3f66af73765670197b417c743c04e3fdb7f47031ead783d98494f1" } } ], "extra": [ 1, 145, 23, 190, 55, 80, 179, 79, 166, 204, 189, 217, 232, 54, 53, 77, 232, 120, 145, 229, 77, 181, 90, 174, 97, 178, 5, 119, 18, 125, 100, 245, 170, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: