Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3830c2a0a167b47b77342cad3537a139eade40d8533ed37ae5ed714d39c16b05

Tx prefix hash: 987e6d51009ca22560f44acafa1ba8a48e87902e02f8cc3a7c6221ec7b52957b
Tx public key: a98506c81b412eba390b0e5b39a9321e0a44315300093992caac42da4fb48afc
Timestamp: 1738641551 Timestamp [UTC]: 2025-02-04 03:59:11 Age [y:d:h:m:s]: 01:008:06:02:17
Block: 1211663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264437 RingCT/type: yes/0
Extra: 01a98506c81b412eba390b0e5b39a9321e0a44315300093992caac42da4fb48afc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ce9e8bd5cf2fb9208fd32756fb6e89ca3371c83690a7838cc758a5f6419d523 0.000600000000 1698426 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": 1211673, "vin": [ { "gen": { "height": 1211663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ce9e8bd5cf2fb9208fd32756fb6e89ca3371c83690a7838cc758a5f6419d523" } } ], "extra": [ 1, 169, 133, 6, 200, 27, 65, 46, 186, 57, 11, 14, 91, 57, 169, 50, 30, 10, 68, 49, 83, 0, 9, 57, 146, 202, 172, 66, 218, 79, 180, 138, 252, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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) | dinastycoin version: tesla-369