Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8aaba30934a65894059c6b1cd8b95ff85fa2cb837f8b43c97ceba81603c87f9

Tx prefix hash: 436651c3fdfbe7a2439a8db6f482b2468488dccffe35a0cb83c20cc90e6e085c
Tx public key: 989c30d7e7aa68504daed90628d70628cce634a9c8f847eeed515cfdf756e53c
Timestamp: 1772594377 Timestamp [UTC]: 2026-03-04 03:19:37 Age [y:d:h:m:s]: 00:259:10:25:21
Block: 1490227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190942 RingCT/type: yes/0
Extra: 01989c30d7e7aa68504daed90628d70628cce634a9c8f847eeed515cfdf756e53c02110000000ae4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6579c677f99ae358fc98fc17a4d32910a3f5a9f2f0475b4cc3e8c81495171934 0.000600000000 1979729 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": 1490237, "vin": [ { "gen": { "height": 1490227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6579c677f99ae358fc98fc17a4d32910a3f5a9f2f0475b4cc3e8c81495171934" } } ], "extra": [ 1, 152, 156, 48, 215, 231, 170, 104, 80, 77, 174, 217, 6, 40, 215, 6, 40, 204, 230, 52, 169, 200, 248, 71, 238, 237, 81, 92, 253, 247, 86, 229, 60, 2, 17, 0, 0, 0, 10, 228, 245, 25, 63, 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: