Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab1a6d55f8831aee289e1b3ae4c6a0fac6a3f79f78fbec3a1bd65bf740566ea2

Tx prefix hash: 98fbcaee10893176669a786837bbe5575a787b8145028f9ba20b6fdffa124361
Tx public key: 90c1f20b409f63d868a6f0d77f707b1ccc5f75ac3f17d0881876e3d7c7008cec
Timestamp: 1770660189 Timestamp [UTC]: 2026-02-09 18:03:09 Age [y:d:h:m:s]: 00:021:15:51:15
Block: 1474235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 15466 RingCT/type: yes/0
Extra: 0190c1f20b409f63d868a6f0d77f707b1ccc5f75ac3f17d0881876e3d7c7008cec0208806282cdcaea3b6b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e2f9801ea2bc774c7788a9bf9dd3d4f10c1d5b1aa9c4eecd5e5bf2443eb18ccd 0.000600000000 1963531 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": 1474245, "vin": [ { "gen": { "height": 1474235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2f9801ea2bc774c7788a9bf9dd3d4f10c1d5b1aa9c4eecd5e5bf2443eb18ccd" } } ], "extra": [ 1, 144, 193, 242, 11, 64, 159, 99, 216, 104, 166, 240, 215, 127, 112, 123, 28, 204, 95, 117, 172, 63, 23, 208, 136, 24, 118, 227, 215, 199, 0, 140, 236, 2, 8, 128, 98, 130, 205, 202, 234, 59, 107 ], "rct_signatures": { "type": 0 } }


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