Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 466fa2871d9bb8804ac4975af7ff531d8fcc5166cc291b7d5b9cb3e9cf6b57ea

Tx prefix hash: c726af47ce33e6a4e171722c326ce78b1173dcfde83f25aca4dd21292d4a97d1
Tx public key: 8c818a407dea3300f1c87c461bfa25aa3a12300ba4cf72dcb82bb4f1e52d7504
Timestamp: 1755303634 Timestamp [UTC]: 2025-08-16 00:20:34 Age [y:d:h:m:s]: 01:095:11:20:49
Block: 1347512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334346 RingCT/type: yes/0
Extra: 018c818a407dea3300f1c87c461bfa25aa3a12300ba4cf72dcb82bb4f1e52d750402110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5edba5057a62b7140339f946a151581fb4dbdb94c70e3dd77a49c54e6054c05a 0.000600000000 1835429 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": 1347522, "vin": [ { "gen": { "height": 1347512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5edba5057a62b7140339f946a151581fb4dbdb94c70e3dd77a49c54e6054c05a" } } ], "extra": [ 1, 140, 129, 138, 64, 125, 234, 51, 0, 241, 200, 124, 70, 27, 250, 37, 170, 58, 18, 48, 11, 164, 207, 114, 220, 184, 43, 180, 241, 229, 45, 117, 4, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: