Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f9a41b6984da75dab78cf196cd5f67c56344760eb18fb45ddedfed935601d7

Tx prefix hash: 7b3482a66326447bf0e7affd7a6e1a77625dd7dd8907d0e4046fc81fe2aa820b
Tx public key: e298196cf34d75ff435c53c7d96ef581071231e51c76c2fa0df09ec2b96cf5b8
Timestamp: 1702508373 Timestamp [UTC]: 2023-12-13 22:59:33 Age [y:d:h:m:s]: 02:148:05:44:48
Block: 912539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 618311 RingCT/type: yes/0
Extra: 01e298196cf34d75ff435c53c7d96ef581071231e51c76c2fa0df09ec2b96cf5b802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 27376c4a5870104922f50abf2bdb8d05f7338a474d966092442102595b94a9ea 0.000600000000 1369767 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": 912549, "vin": [ { "gen": { "height": 912539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27376c4a5870104922f50abf2bdb8d05f7338a474d966092442102595b94a9ea" } } ], "extra": [ 1, 226, 152, 25, 108, 243, 77, 117, 255, 67, 92, 83, 199, 217, 110, 245, 129, 7, 18, 49, 229, 28, 118, 194, 250, 13, 240, 158, 194, 185, 108, 245, 184, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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: