Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3c525f21ca2ad33e679c62080ebf82fb8ba7c0f4227eee10f6fa4deeef40773

Tx prefix hash: a0deaf0b02d908019427ba04b14b8458905b1f829802fcd4a67ddc22dbd763d2
Tx public key: fc6d138073ad173c25546d3d06a7583d2fdf2fe24713c50ce6ece3d83c9940d0
Timestamp: 1772897704 Timestamp [UTC]: 2026-03-07 15:35:04 Age [y:d:h:m:s]: 00:250:07:35:42
Block: 1492743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184227 RingCT/type: yes/0
Extra: 01fc6d138073ad173c25546d3d06a7583d2fdf2fe24713c50ce6ece3d83c9940d0021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f67b8871b6183fe4de042fd13ffc1ef55ed5c517b5b0ddba1efd081d80a577ef 0.000600000000 1982293 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": 1492753, "vin": [ { "gen": { "height": 1492743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f67b8871b6183fe4de042fd13ffc1ef55ed5c517b5b0ddba1efd081d80a577ef" } } ], "extra": [ 1, 252, 109, 19, 128, 115, 173, 23, 60, 37, 84, 109, 61, 6, 167, 88, 61, 47, 223, 47, 226, 71, 19, 197, 12, 230, 236, 227, 216, 60, 153, 64, 208, 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: