Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4991b1e78aa0702fb8c868a1ce5af621ea0e5657accda6dcadb0ce6dad16bfbd

Tx prefix hash: 17311876626e216383207848f32084338e819e791658fe31151c1fdd05b13317
Tx public key: 889405d454fad7ee96c972a529f4e60d37a7036e08e5ed5b385b1309817fdb8b
Timestamp: 1755844462 Timestamp [UTC]: 2025-08-22 06:34:22 Age [y:d:h:m:s]: 00:260:16:31:54
Block: 1351796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178888 RingCT/type: yes/0
Extra: 01889405d454fad7ee96c972a529f4e60d37a7036e08e5ed5b385b1309817fdb8b021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7aa8ff49c7efa8d3877097543659f7ebbfc050949b5c2f6cdf215c8bbfc0d615 0.000600000000 1839753 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": 1351806, "vin": [ { "gen": { "height": 1351796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa8ff49c7efa8d3877097543659f7ebbfc050949b5c2f6cdf215c8bbfc0d615" } } ], "extra": [ 1, 136, 148, 5, 212, 84, 250, 215, 238, 150, 201, 114, 165, 41, 244, 230, 13, 55, 167, 3, 110, 8, 229, 237, 91, 56, 91, 19, 9, 129, 127, 219, 139, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: