Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e9bdb9a72b8d8c1a032de9686370481cb8b82f2b9ce04f1ce8811b51d310944

Tx prefix hash: 01b3bd4ea62aaf73ee25e84ed4a876c99a4a26ed670e366034b2ce9ca9108f69
Tx public key: 7ef163f3afe4c7418d43b84f19b74af38f5d810c2e4ee5adc590964dd6d894ef
Timestamp: 1739825038 Timestamp [UTC]: 2025-02-17 20:43:58 Age [y:d:h:m:s]: 01:277:17:52:53
Block: 1221440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462054 RingCT/type: yes/0
Extra: 017ef163f3afe4c7418d43b84f19b74af38f5d810c2e4ee5adc590964dd6d894ef021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e29e0dabf9b83c7aa7b5e47d3dbeaa67fa7dfee7b10c28867778a156fad95ad2 0.000600000000 1708285 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": 1221450, "vin": [ { "gen": { "height": 1221440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e29e0dabf9b83c7aa7b5e47d3dbeaa67fa7dfee7b10c28867778a156fad95ad2" } } ], "extra": [ 1, 126, 241, 99, 243, 175, 228, 199, 65, 141, 67, 184, 79, 25, 183, 74, 243, 143, 93, 129, 12, 46, 78, 229, 173, 197, 144, 150, 77, 214, 216, 148, 239, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: