Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6977ba32090fc0e1e392e81282a644efb331e531a435e96ac5e2f5cc3030f5b6

Tx prefix hash: 4bf585cb42b654e65d57bfdd0b0f3243e77baf4ef1f8961069fa334c545cc1cc
Tx public key: 9a31d2670c7cb4a86e36a3f0d0193c3f53fb009c80e6adb653598a56d36d4a4d
Timestamp: 1773831367 Timestamp [UTC]: 2026-03-18 10:56:07 Age [y:d:h:m:s]: 00:242:07:12:45
Block: 1500434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178634 RingCT/type: yes/0
Extra: 019a31d2670c7cb4a86e36a3f0d0193c3f53fb009c80e6adb653598a56d36d4a4d021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df8ff6345f7208c640888408b0ee1805cf3e396d654c9534775b02ef9d763f25 0.000600000000 1990106 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": 1500444, "vin": [ { "gen": { "height": 1500434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df8ff6345f7208c640888408b0ee1805cf3e396d654c9534775b02ef9d763f25" } } ], "extra": [ 1, 154, 49, 210, 103, 12, 124, 180, 168, 110, 54, 163, 240, 208, 25, 60, 63, 83, 251, 0, 156, 128, 230, 173, 182, 83, 89, 138, 86, 211, 109, 74, 77, 2, 17, 0, 0, 0, 8, 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: