Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549841e8a456a216675fcbefd9b6c6e924fdf3be2aa04348d1d2a0dae3065666

Tx prefix hash: 7305629cd8c9e19a8304c47859a53d8bf649f0eaf318003d55bad5bfed4e8446
Tx public key: 069e31ed1a765a926eb3171afa40384b4fd50f33543a1976b288540cbe62c3bc
Timestamp: 1758528076 Timestamp [UTC]: 2025-09-22 08:01:16 Age [y:d:h:m:s]: 01:058:14:51:10
Block: 1373863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308358 RingCT/type: yes/0
Extra: 01069e31ed1a765a926eb3171afa40384b4fd50f33543a1976b288540cbe62c3bc021100000006ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 071c800da777d2f66d032a7fe036e5d4d37d48901e9e9d54644ef40713d3cf01 0.000600000000 1861948 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": 1373873, "vin": [ { "gen": { "height": 1373863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "071c800da777d2f66d032a7fe036e5d4d37d48901e9e9d54644ef40713d3cf01" } } ], "extra": [ 1, 6, 158, 49, 237, 26, 118, 90, 146, 110, 179, 23, 26, 250, 64, 56, 75, 79, 213, 15, 51, 84, 58, 25, 118, 178, 136, 84, 12, 190, 98, 195, 188, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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: