Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e21553a7ef00b7bbafcddc15356bfc69da61890011a2a51f4cc4c28cebeba8

Tx prefix hash: f036e0ce88bd13d15f639fa4a7ee304240413e87c6d23851c37aac3f4b3cec02
Tx public key: 10f8351ea94593ba89e62bff27b81b2c117c8d937c0d93cd9a2724ffd8cf7e16
Timestamp: 1733128692 Timestamp [UCT]: 2024-12-02 08:38:12 Age [y:d:h:m:s]: 00:196:01:10:13
Block: 1166298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139862 RingCT/type: yes/0
Extra: 0110f8351ea94593ba89e62bff27b81b2c117c8d937c0d93cd9a2724ffd8cf7e16021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cffe300b693d8e300c0edf3e0ed1c574f4b761005a3c9825dedf35541190679 0.600000000000 1651975 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": 1166308, "vin": [ { "gen": { "height": 1166298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cffe300b693d8e300c0edf3e0ed1c574f4b761005a3c9825dedf35541190679" } } ], "extra": [ 1, 16, 248, 53, 30, 169, 69, 147, 186, 137, 230, 43, 255, 39, 184, 27, 44, 17, 124, 141, 147, 124, 13, 147, 205, 154, 39, 36, 255, 216, 207, 126, 22, 2, 17, 0, 0, 0, 1, 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