Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4660f5a5efa2edac3a8890ec9b41a1fd0d435cee1f13c8ca119c45dba1a932f

Tx prefix hash: 92469b6ecf929b20cf7afb89d65686a820b7bd53ce29e08e38309fe4eb173f70
Tx public key: dec06852bfc29fbcf9839c08f52c043fec40ed2d51aa803df255806576914e61
Timestamp: 1743722897 Timestamp [UTC]: 2025-04-03 23:28:17 Age [y:d:h:m:s]: 01:107:08:46:05
Block: 1253734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329380 RingCT/type: yes/0
Extra: 01dec06852bfc29fbcf9839c08f52c043fec40ed2d51aa803df255806576914e61021100000003a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b415a6806b05ed624fe64d5e9a3b1de7928b483b2722decfaa91f5c507870fdf 0.000600000000 1740815 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": 1253744, "vin": [ { "gen": { "height": 1253734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b415a6806b05ed624fe64d5e9a3b1de7928b483b2722decfaa91f5c507870fdf" } } ], "extra": [ 1, 222, 192, 104, 82, 191, 194, 159, 188, 249, 131, 156, 8, 245, 44, 4, 63, 236, 64, 237, 45, 81, 170, 128, 61, 242, 85, 128, 101, 118, 145, 78, 97, 2, 17, 0, 0, 0, 3, 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: