Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f98f51b5b22b106b37d97953138dcb9780bca7d3e6e7b4fe67b2d9f6f6d7a4

Tx prefix hash: 46713065df247e461d8b7ed48b10cbc4b5972433e04d89a96fbdec84b79e929d
Tx public key: 94db61caa0ef358f396f500bf2d34de831ce57c92f25a2d055085d09724ef05c
Timestamp: 1770337781 Timestamp [UTC]: 2026-02-06 00:29:41 Age [y:d:h:m:s]: 00:001:02:27:53
Block: 1471570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 792 RingCT/type: yes/0
Extra: 0194db61caa0ef358f396f500bf2d34de831ce57c92f25a2d055085d09724ef05c02088a8eff4ac93ad3b1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 047b38f521389dd2f7b9f1442e079fa70c5214004c9c7600f42d2baf2f8826a5 0.000600000000 1960842 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": 1471580, "vin": [ { "gen": { "height": 1471570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "047b38f521389dd2f7b9f1442e079fa70c5214004c9c7600f42d2baf2f8826a5" } } ], "extra": [ 1, 148, 219, 97, 202, 160, 239, 53, 143, 57, 111, 80, 11, 242, 211, 77, 232, 49, 206, 87, 201, 47, 37, 162, 208, 85, 8, 93, 9, 114, 78, 240, 92, 2, 8, 138, 142, 255, 74, 201, 58, 211, 177 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369