Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb8e3e07adebd43a01930a4bee65f2734d71a6848522b36c6ebe26af0297f67

Tx prefix hash: 2e825111f97d55c4817c11c4800c7d59cdfc50ff5cb0f01fcc7234f0f27ac457
Tx public key: 5f9dd10ed73ba013bf56e925df962095ca4cc16e99277e2174422fdd535328ed
Timestamp: 1735048287 Timestamp [UTC]: 2024-12-24 13:51:27 Age [y:d:h:m:s]: 01:138:05:29:55
Block: 1182198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349340 RingCT/type: yes/0
Extra: 015f9dd10ed73ba013bf56e925df962095ca4cc16e99277e2174422fdd535328ed0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 266053ef093eda0296ad4994a6c98d3e746c41a5e50cdf1cc4f89332ba2c368a 0.000600000000 1668631 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": 1182208, "vin": [ { "gen": { "height": 1182198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "266053ef093eda0296ad4994a6c98d3e746c41a5e50cdf1cc4f89332ba2c368a" } } ], "extra": [ 1, 95, 157, 209, 14, 215, 59, 160, 19, 191, 86, 233, 37, 223, 150, 32, 149, 202, 76, 193, 110, 153, 39, 126, 33, 116, 66, 47, 221, 83, 83, 40, 237, 2, 17, 0, 0, 0, 1, 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: