Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644ee80274e1990c52c33896664a50bead13dce928c8c5ccb40b386f28801964

Tx prefix hash: 6488ebbcbce5ab6bac9c2b3b01258bdb50a7388a9d917fb551360e77b988b94e
Tx public key: f57daf4936882fb1032c49a6a331453adf5e048623e510b36d64aa5e5abcde1d
Timestamp: 1724683518 Timestamp [UCT]: 2024-08-26 14:45:18 Age [y:d:h:m:s]: 01:077:01:54:35
Block: 1096381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313536 RingCT/type: yes/0
Extra: 01f57daf4936882fb1032c49a6a331453adf5e048623e510b36d64aa5e5abcde1d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca5524cb1ae472727a6bc1e22008c11c879c33c87b86be9083e37872730aa285 0.600000000000 1571570 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": 1096391, "vin": [ { "gen": { "height": 1096381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca5524cb1ae472727a6bc1e22008c11c879c33c87b86be9083e37872730aa285" } } ], "extra": [ 1, 245, 125, 175, 73, 54, 136, 47, 177, 3, 44, 73, 166, 163, 49, 69, 58, 223, 94, 4, 134, 35, 229, 16, 179, 109, 100, 170, 94, 90, 188, 222, 29, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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