Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f392d17743174a8afc52c19f27c3ef63a1b1011b335820175cea9d6312eae36

Tx prefix hash: cb1df462caa44df5665a4526ece2c13b402f9a275b686e88900d22072e34ed8b
Tx public key: 09b93cfd1a13c0f6e54be1808cd1373d61f6a407c8beb7aa039eb036df390dd5
Timestamp: 1737972043 Timestamp [UCT]: 2025-01-27 10:00:43 Age [y:d:h:m:s]: 00:046:05:58:17
Block: 1206153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33077 RingCT/type: yes/0
Extra: 0109b93cfd1a13c0f6e54be1808cd1373d61f6a407c8beb7aa039eb036df390dd50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab5f5443b2821238effee2cdf8652e544bfdfc75f8c64173558185a9b58cd960 0.600000000000 1692856 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": 1206163, "vin": [ { "gen": { "height": 1206153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab5f5443b2821238effee2cdf8652e544bfdfc75f8c64173558185a9b58cd960" } } ], "extra": [ 1, 9, 185, 60, 253, 26, 19, 192, 246, 229, 75, 225, 128, 140, 209, 55, 61, 97, 246, 164, 7, 200, 190, 183, 170, 3, 158, 176, 54, 223, 57, 13, 213, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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