Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a677830393eb75284e31c0cc6d14a01db2c60af27d6a8f1deb74e0d73aaea604

Tx prefix hash: 9359149e806ac22587bb810f28ce2d344d851125e244ed80ce2d8b33e643e6b3
Tx public key: f3407da2754173b2cee5fb3b7c88dc16213412645411034560184d24ee96a97a
Timestamp: 1740401000 Timestamp [UTC]: 2025-02-24 12:43:20 Age [y:d:h:m:s]: 01:077:19:40:54
Block: 1226218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306507 RingCT/type: yes/0
Extra: 01f3407da2754173b2cee5fb3b7c88dc16213412645411034560184d24ee96a97a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 344de121ad69a9cdba664d6df3ffd99facc497a7d009c832e8da45a431a5e8e6 0.000600000000 1713089 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": 1226228, "vin": [ { "gen": { "height": 1226218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "344de121ad69a9cdba664d6df3ffd99facc497a7d009c832e8da45a431a5e8e6" } } ], "extra": [ 1, 243, 64, 125, 162, 117, 65, 115, 178, 206, 229, 251, 59, 124, 136, 220, 22, 33, 52, 18, 100, 84, 17, 3, 69, 96, 24, 77, 36, 238, 150, 169, 122, 2, 17, 0, 0, 0, 2, 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: