Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c08527223aad0b0a5185144348e74b388dee99d1d61febbdb1b57ace58e43b05

Tx prefix hash: 6939f87c9425543e14e8406c6b9a5234bdb9df6ba35c348da46e2618e71b3d27
Tx public key: c021e9a1f0d1636f5144e5919b54b563f18b3aa10be229f43b1be7939196c3a0
Timestamp: 1737643208 Timestamp [UCT]: 2025-01-23 14:40:08 Age [y:d:h:m:s]: 00:301:17:05:31
Block: 1203636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213164 RingCT/type: yes/0
Extra: 01c021e9a1f0d1636f5144e5919b54b563f18b3aa10be229f43b1be7939196c3a0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d941968ab8518e97761dd33bcc61b4fcafc9c9aa1e14cd9ac72077cfd8456c8 0.600000000000 1690315 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": 1203646, "vin": [ { "gen": { "height": 1203636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d941968ab8518e97761dd33bcc61b4fcafc9c9aa1e14cd9ac72077cfd8456c8" } } ], "extra": [ 1, 192, 33, 233, 161, 240, 209, 99, 111, 81, 68, 229, 145, 155, 84, 181, 99, 241, 139, 58, 161, 11, 226, 41, 244, 59, 27, 231, 147, 145, 150, 195, 160, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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