Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f605976130e3d6365060eefab26496bfde0f9c2b1fd64235951d828a009a08f2

Tx prefix hash: 5cd1d1732a4f55d02f1c405e2c4411f76f02996f4276399e451b9f2cf50f4523
Tx public key: 2f78d0f4ba866804cc5e64616a10f09090168a53623471a7f5f3dceed249e5ad
Timestamp: 1709265966 Timestamp [UCT]: 2024-03-01 04:06:06 Age [y:d:h:m:s]: 01:084:23:45:17
Block: 968569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321786 RingCT/type: yes/0
Extra: 012f78d0f4ba866804cc5e64616a10f09090168a53623471a7f5f3dceed249e5ad0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e823374b17e72c4844e3018cb12ad2cf1db31fc39858ccb15ea39ecd5111c2e 0.600000000000 1428386 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": 968579, "vin": [ { "gen": { "height": 968569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e823374b17e72c4844e3018cb12ad2cf1db31fc39858ccb15ea39ecd5111c2e" } } ], "extra": [ 1, 47, 120, 208, 244, 186, 134, 104, 4, 204, 94, 100, 97, 106, 16, 240, 144, 144, 22, 138, 83, 98, 52, 113, 167, 245, 243, 220, 238, 210, 73, 229, 173, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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