Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cfecd36885cd47cc397ad10c8fbfe6b951e49da1c447b51fb2433c324a17aba

Tx prefix hash: e4974aa08ed6315a2f2701cf2002ec85cf944b21fc38f51099c833cd705ab0cd
Tx public key: 9ea1165310c5a62a2cbd524142cb84e529ed9ee996e102a6ab7be064be8e4a95
Timestamp: 1738340956 Timestamp [UTC]: 2025-01-31 16:29:16 Age [y:d:h:m:s]: 01:162:17:18:11
Block: 1209184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372066 RingCT/type: yes/0
Extra: 019ea1165310c5a62a2cbd524142cb84e529ed9ee996e102a6ab7be064be8e4a950211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 59991771d43022d5ac6e161b5df6efa62c118ef46fc386af5fdf59f7163d802b 0.000600000000 1695925 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": 1209194, "vin": [ { "gen": { "height": 1209184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59991771d43022d5ac6e161b5df6efa62c118ef46fc386af5fdf59f7163d802b" } } ], "extra": [ 1, 158, 161, 22, 83, 16, 197, 166, 42, 44, 189, 82, 65, 66, 203, 132, 229, 41, 237, 158, 233, 150, 225, 2, 166, 171, 123, 224, 100, 190, 142, 74, 149, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: