Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e843490e5b0546db0a973058f622dc27d2bcf233549752b9b56e2a886bb08f6

Tx prefix hash: d33620273571510dd0b08fce9984317c5e997a6c6091ec0937a9714ae63fd61f
Tx public key: 5cf5719cc7d9ccd4fd73363818057ce820b54891a7aa341096a3b477bf09b254
Timestamp: 1709165635 Timestamp [UTC]: 2024-02-29 00:13:55 Age [y:d:h:m:s]: 02:267:08:09:47
Block: 967740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715754 RingCT/type: yes/0
Extra: 015cf5719cc7d9ccd4fd73363818057ce820b54891a7aa341096a3b477bf09b2540211000000070011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: acb9f774bbb5b5ed194451b361ad3a6779c22b99e32eb2899bc8b19ddafb91ae 0.000600000000 1427525 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": 967750, "vin": [ { "gen": { "height": 967740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acb9f774bbb5b5ed194451b361ad3a6779c22b99e32eb2899bc8b19ddafb91ae" } } ], "extra": [ 1, 92, 245, 113, 156, 199, 217, 204, 212, 253, 115, 54, 56, 24, 5, 124, 232, 32, 181, 72, 145, 167, 170, 52, 16, 150, 163, 180, 119, 191, 9, 178, 84, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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: