Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abb315f1cb7c0afb0e104648c8a06fcef8980b6fbafdb09b02f5526e17dadba5

Tx prefix hash: 421ddd5c43af56a1d3ecddad9d8782082bf61070fd86f185a9c22dcb2656d134
Tx public key: 6467d701ad14fdac2e5a9d86afdd8b7fdf4ea8a6d5c95a092e76caec22406e02
Timestamp: 1759064309 Timestamp [UTC]: 2025-09-28 12:58:29 Age [y:d:h:m:s]: 01:045:14:49:17
Block: 1378298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298821 RingCT/type: yes/0
Extra: 016467d701ad14fdac2e5a9d86afdd8b7fdf4ea8a6d5c95a092e76caec22406e02021100000008a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ef03130b374fd93f2c92788c5ea5679d95d375699a83a8d97368aef9a1bc4540 0.000600000000 1866393 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": 1378308, "vin": [ { "gen": { "height": 1378298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef03130b374fd93f2c92788c5ea5679d95d375699a83a8d97368aef9a1bc4540" } } ], "extra": [ 1, 100, 103, 215, 1, 173, 20, 253, 172, 46, 90, 157, 134, 175, 221, 139, 127, 223, 78, 168, 166, 213, 201, 90, 9, 46, 118, 202, 236, 34, 64, 110, 2, 2, 17, 0, 0, 0, 8, 165, 220, 205, 121, 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: