Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f9e192001deb6344d5b653bd154a457f301aa62347363d1d0a225ac08d575bb

Tx prefix hash: ffc3d3ccbac6d45f0de9da4d9a4d9d223d1144a57b2e3b748fe9fd91933154dc
Tx public key: 0c85dd8c5dc0b0ddfcb3d2ecab1c7c6c45cbae8bc64130b7c861456c1cf52e4e
Timestamp: 1774204737 Timestamp [UTC]: 2026-03-22 18:38:57 Age [y:d:h:m:s]: 00:244:05:37:42
Block: 1503525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179969 RingCT/type: yes/0
Extra: 010c85dd8c5dc0b0ddfcb3d2ecab1c7c6c45cbae8bc64130b7c861456c1cf52e4e021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1de33830e9c685d61b440705e93eeffa8ac2f71acca7f4017646a436738886f6 0.000600000000 1993237 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": 1503535, "vin": [ { "gen": { "height": 1503525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1de33830e9c685d61b440705e93eeffa8ac2f71acca7f4017646a436738886f6" } } ], "extra": [ 1, 12, 133, 221, 140, 93, 192, 176, 221, 252, 179, 210, 236, 171, 28, 124, 108, 69, 203, 174, 139, 198, 65, 48, 183, 200, 97, 69, 108, 28, 245, 46, 78, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: