Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1c57d8a1f768afb6bb9ddf0cf14a9d2dd25747fbbe24558a9c2b3b78316efb

Tx prefix hash: a267b1abfb3cae810a320d4cc36875b2b9f674f145522aa78dd4160ff9668493
Tx public key: a2548810944025841c8d6c0f5eddb1625cdfb62f41dbf76ec0899a1b0a691dc6
Timestamp: 1771912419 Timestamp [UTC]: 2026-02-24 05:53:39 Age [y:d:h:m:s]: 00:268:17:00:30
Block: 1484584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197639 RingCT/type: yes/0
Extra: 01a2548810944025841c8d6c0f5eddb1625cdfb62f41dbf76ec0899a1b0a691dc6021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 859e0eafa92436946e3256e899a2cea1ab1fa62c9ca317f8926ac1f1d67b318a 0.000600000000 1974010 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": 1484594, "vin": [ { "gen": { "height": 1484584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "859e0eafa92436946e3256e899a2cea1ab1fa62c9ca317f8926ac1f1d67b318a" } } ], "extra": [ 1, 162, 84, 136, 16, 148, 64, 37, 132, 28, 141, 108, 15, 94, 221, 177, 98, 92, 223, 182, 47, 65, 219, 247, 110, 192, 137, 154, 27, 10, 105, 29, 198, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: