Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e995dfba1abb202de7726d535af316d10a634e9c7dbb072bd58cc9666cebb476

Tx prefix hash: c72107ffc85f88717230ee1e5ad30cbd6b1ce1656b86a2d8e607fe7ac353524e
Tx public key: 6e2c4f864ad5c69411c58a9380b70c7f824be50285c719f25c34aba8d36909dc
Timestamp: 1746950699 Timestamp [UTC]: 2025-05-11 08:04:59 Age [y:d:h:m:s]: 01:007:15:00:15
Block: 1280463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256652 RingCT/type: yes/0
Extra: 016e2c4f864ad5c69411c58a9380b70c7f824be50285c719f25c34aba8d36909dc0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4121c5c11290708e08bdb57ed00f1b29d62798adc42d9a8cb0595fad7e7eb088 0.000600000000 1767850 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": 1280473, "vin": [ { "gen": { "height": 1280463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4121c5c11290708e08bdb57ed00f1b29d62798adc42d9a8cb0595fad7e7eb088" } } ], "extra": [ 1, 110, 44, 79, 134, 74, 213, 198, 148, 17, 197, 138, 147, 128, 183, 12, 127, 130, 75, 229, 2, 133, 199, 25, 242, 92, 52, 171, 168, 211, 105, 9, 220, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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: