Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52156de70dee2e1d5cb3370061791c35b257d50458fd88e75d2aba378c16a87f

Tx prefix hash: e229ea9eb3a3b4f1e381621cd4b3cb1fdf9c10c161f0b6fb04d2ce3059141e39
Tx public key: 81684a7ce9ec80e90421810eb9b98e56ee24240e9bbd94a6362b444bfd4e2990
Timestamp: 1744379869 Timestamp [UTC]: 2025-04-11 13:57:49 Age [y:d:h:m:s]: 01:100:08:23:43
Block: 1259180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323934 RingCT/type: yes/0
Extra: 0181684a7ce9ec80e90421810eb9b98e56ee24240e9bbd94a6362b444bfd4e2990021100000026dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2d7455061e4cd53f337150f4a85e29d93673a06536ed1bac94adc792368e1238 0.000600000000 1746319 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": 1259190, "vin": [ { "gen": { "height": 1259180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7455061e4cd53f337150f4a85e29d93673a06536ed1bac94adc792368e1238" } } ], "extra": [ 1, 129, 104, 74, 124, 233, 236, 128, 233, 4, 33, 129, 14, 185, 185, 142, 86, 238, 36, 36, 14, 155, 189, 148, 166, 54, 43, 68, 75, 253, 78, 41, 144, 2, 17, 0, 0, 0, 38, 219, 181, 113, 193, 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: