Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233d695ec3c8d6616b22e338bf7a6881265a8bea4468b05a2d865d74ebc33caa

Tx prefix hash: 41d6ce97f7df1c5d1ea4474fd50d3f52bb3aa62e5f904f5234977324a5a8704f
Tx public key: a45a633a69d18452bdd312692af359e7e5350a7052a4a1fc89de4c63ccd4189a
Timestamp: 1771171031 Timestamp [UTC]: 2026-02-15 15:57:11 Age [y:d:h:m:s]: 00:274:06:09:24
Block: 1478433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201517 RingCT/type: yes/0
Extra: 01a45a633a69d18452bdd312692af359e7e5350a7052a4a1fc89de4c63ccd4189a021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b0f3a0df765e387ebc642ace3af66584e38ba84e9a0f86d8a838cb6a9b706829 0.000600000000 1967763 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": 1478443, "vin": [ { "gen": { "height": 1478433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f3a0df765e387ebc642ace3af66584e38ba84e9a0f86d8a838cb6a9b706829" } } ], "extra": [ 1, 164, 90, 99, 58, 105, 209, 132, 82, 189, 211, 18, 105, 42, 243, 89, 231, 229, 53, 10, 112, 82, 164, 161, 252, 137, 222, 76, 99, 204, 212, 24, 154, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: