Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f80f3b56e79d3962fee0487c46e17910674fd8cfb8e622ae8057d35b7f946e

Tx prefix hash: 39da94f42d1e510fc47e78abbdeadc3392cd230e9e7d31a23017ed2faaaa3a69
Tx public key: 2a5f4108a2d5b7ab75e2484f8f4ed0f0d29819d8b41049f24c9b2ca6e541c6c2
Timestamp: 1736736566 Timestamp [UCT]: 2025-01-13 02:49:26 Age [y:d:h:m:s]: 00:158:04:56:30
Block: 1196164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112734 RingCT/type: yes/0
Extra: 012a5f4108a2d5b7ab75e2484f8f4ed0f0d29819d8b41049f24c9b2ca6e541c6c20211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cfb0d1a5d32faaf91d2f0bbda6244b5287950e71fb8e895f6e85aab6e81c9d2 0.600000000000 1682761 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 dinasty-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": 1196174, "vin": [ { "gen": { "height": 1196164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cfb0d1a5d32faaf91d2f0bbda6244b5287950e71fb8e895f6e85aab6e81c9d2" } } ], "extra": [ 1, 42, 95, 65, 8, 162, 213, 183, 171, 117, 226, 72, 79, 143, 78, 208, 240, 210, 152, 25, 216, 180, 16, 73, 242, 76, 155, 44, 166, 229, 65, 198, 194, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8