Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0819e44cd5fff2b2e5d9e001f579289d96e9ca9f6cf524fcd0eb3bfd27441f6

Tx prefix hash: 0ef5116cbdf9ed7c402b4c8278a62622f758d4d796cc078a1251d8c62c96baa5
Tx public key: 3ef94fcaa2056d595fa329c3b4ef2e5d13e8734e8c56fdd867b72ddd85e8035e
Timestamp: 1772246600 Timestamp [UTC]: 2026-02-28 02:43:20 Age [y:d:h:m:s]: 00:263:22:49:42
Block: 1487337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194199 RingCT/type: yes/0
Extra: 013ef94fcaa2056d595fa329c3b4ef2e5d13e8734e8c56fdd867b72ddd85e8035e021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 155f2cb55b6debd8896500e3756f8993fb8988584c42e5b1c6519b20266a6a79 0.000600000000 1976805 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": 1487347, "vin": [ { "gen": { "height": 1487337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "155f2cb55b6debd8896500e3756f8993fb8988584c42e5b1c6519b20266a6a79" } } ], "extra": [ 1, 62, 249, 79, 202, 162, 5, 109, 89, 95, 163, 41, 195, 180, 239, 46, 93, 19, 232, 115, 78, 140, 86, 253, 216, 103, 183, 45, 221, 133, 232, 3, 94, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: