Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4134c11bf1be7392a6d80a1cbc3b29ff6a84d086cc35e58a039c5809d6eb3e7b

Tx prefix hash: a678a9953e73b05ed43767be6bbee7787089ca6f96288a0367b20f3d407cc0a1
Tx public key: a569fbe61b0b5e69d0123b3359c37649ddf3ca946572755a1479d1478e653a16
Timestamp: 1769782713 Timestamp [UTC]: 2026-01-30 14:18:33 Age [y:d:h:m:s]: 00:103:22:13:02
Block: 1466948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66652 RingCT/type: yes/0
Extra: 01a569fbe61b0b5e69d0123b3359c37649ddf3ca946572755a1479d1478e653a16021100000009215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a21ead5e3a961cecb594f968a4f230bc8a44bec649f8ee49499bef39e021fdf 0.000600000000 1956188 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": 1466958, "vin": [ { "gen": { "height": 1466948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a21ead5e3a961cecb594f968a4f230bc8a44bec649f8ee49499bef39e021fdf" } } ], "extra": [ 1, 165, 105, 251, 230, 27, 11, 94, 105, 208, 18, 59, 51, 89, 195, 118, 73, 221, 243, 202, 148, 101, 114, 117, 90, 20, 121, 209, 71, 142, 101, 58, 22, 2, 17, 0, 0, 0, 9, 33, 91, 191, 137, 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: