Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e5a127d816f9b6cce31f17003be85cfa9b583ef6f498bb37004783dc4c92fb

Tx prefix hash: 254db3ea7de57137531e17594f9597ba81f1e77a4ae68a9d491a6f1891f4cb44
Tx public key: afae32dfe86d933360fc853b897d43d4f477c0aa5d6fb4b204982bd1190c920a
Timestamp: 1743714034 Timestamp [UTC]: 2025-04-03 21:00:34 Age [y:d:h:m:s]: 01:039:14:08:02
Block: 1253658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279147 RingCT/type: yes/0
Extra: 01afae32dfe86d933360fc853b897d43d4f477c0aa5d6fb4b204982bd1190c920a021100000010a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6fe03b91386513e416a50403bf743a73b3eaa4e8845cf68dff660f930071e38 0.000600000000 1740739 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": 1253668, "vin": [ { "gen": { "height": 1253658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6fe03b91386513e416a50403bf743a73b3eaa4e8845cf68dff660f930071e38" } } ], "extra": [ 1, 175, 174, 50, 223, 232, 109, 147, 51, 96, 252, 133, 59, 137, 125, 67, 212, 244, 119, 192, 170, 93, 111, 180, 178, 4, 152, 43, 209, 25, 12, 146, 10, 2, 17, 0, 0, 0, 16, 162, 237, 1, 107, 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: